From bugmaster at FreeBSD.org Mon Nov 3 03:06:50 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 3 03:07:29 2008 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200811031106.mA3B6oX3010855@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/15876 embedded [picobsd] PicoBSD message of the day problems 4 problems total. From philip.mullis at syx.ca Tue Nov 4 08:20:48 2008 From: philip.mullis at syx.ca (Philip Mullis) Date: Tue Nov 4 08:20:54 2008 Subject: problem with tinybsd on 8-current Message-ID: <49107661.8050908@syx.ca> When running the tinybsd script on 8-current it stops with the following error (seemingly to do with ppp_tty) has anyone else come across this error and know how to correct it? thanks =========== /usr/src/sys/net/ppp_tty.c:150: error: variable 'pppdisc' has initializer but incomplete type cc1: warnings being treated as errors /usr/src/sys/net/ppp_tty.c:151: warning: excess elements in struct initializer /usr/src/sys/net/ppp_tty.c:151: warning: (near initialization for 'pppdisc') /usr/src/sys/net/ppp_tty.c:855: error: 'struct tty' has no member named 't_cc' /usr/src/sys/net/ppp_tty.c:856: error: 'struct tty' has no member named 't_state' [a whack more lines regarding ppp_tty] *** Error code 1 Stop in /usr/obj/usr/src/sys/TINYBSD. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. From stas at FreeBSD.org Tue Nov 4 09:38:11 2008 From: stas at FreeBSD.org (Stanislav Sedov) Date: Tue Nov 4 10:09:56 2008 Subject: problem with tinybsd on 8-current In-Reply-To: <49107661.8050908@syx.ca> References: <49107661.8050908@syx.ca> Message-ID: <20081104203903.6e1816ca.stas@FreeBSD.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 04 Nov 2008 11:20:49 -0500 Philip Mullis mentioned: > When running the tinybsd script on 8-current it stops with the following > error (seemingly to do with ppp_tty) has anyone else come across this > error and know how to correct it? > I think ppp doesn't work on HEAD currently due to MPSAFE tty work. Just disable it in kernel config, and it should build ok. - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkQiLwACgkQK/VZk+smlYGN7gCggF36RcxeLXJUZ6B667Vn2+M/ c8IAnjKsuPMS01MrG+01iaIIuFD+NdJ7 =jt9I -----END PGP SIGNATURE----- From bugmaster at FreeBSD.org Mon Nov 10 03:06:48 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 10 03:07:38 2008 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200811101106.mAAB6mqB049670@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/15876 embedded [picobsd] PicoBSD message of the day problems 4 problems total. From mah at jump-ing.de Mon Nov 10 05:02:09 2008 From: mah at jump-ing.de (Markus Hitter) Date: Mon Nov 10 05:02:17 2008 Subject: FreeBSD kompakt In-Reply-To: <40D69C3A-16B9-4370-B9D5-FCD6FDF87EE4@jump-ing.de> References: <40D69C3A-16B9-4370-B9D5-FCD6FDF87EE4@jump-ing.de> Message-ID: Am 29.10.2008 um 23:11 schrieb Markus Hitter: > Please let me know what you think about this and which parts I > should extract as a precise patch for inclusion in FreeBSD. Any comments on this? Did somebody try? MarKus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ From gleizzer at nti.ufop.br Wed Nov 12 15:12:17 2008 From: gleizzer at nti.ufop.br (GLEIZER VITOR) Date: Wed Nov 12 15:12:23 2008 Subject: NanoBSD boot problem Message-ID: <7081d84f31b719bbacd94ff7ce15675f@cedro.ufop.br> Hi everybody, When I try to boot Nanobsd, it returns this error: ? Nov 12 20:03:53? kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Nov 12 20:03:53? kernel: da0: Removable Direct Access SCSI-2 device Nov 12 20:03:53? kernel: da0: 40.000MB/s transfers Nov 12 20:03:53? kernel: da0: 963MB (1974271 512 byte sectors: 64H 32S/T 963C) Nov 12 20:03:53? kernel: Trying to mount root from ufs:/dev/ad0s1a Nov 12 20:03:53? kernel: Nov 12 20:03:53? kernel: Manual root filesystem specification: Nov 12 20:03:53? kernel: :? Mount using filesystem Nov 12 20:03:53? kernel: eg. ufs:da0s1a Nov 12 20:03:53? kernel: ?????????????????? List valid disk boot devices Nov 12 20:03:53? kernel: ?????? Abort manual input ? And manually doesn?t work, too. Any idea? Thanks ? Gleizer From sbruno at miralink.com Thu Nov 13 09:30:37 2008 From: sbruno at miralink.com (Sean Bruno) Date: Thu Nov 13 09:30:43 2008 Subject: NanoBSD boot problem In-Reply-To: <7081d84f31b719bbacd94ff7ce15675f@cedro.ufop.br> References: <7081d84f31b719bbacd94ff7ce15675f@cedro.ufop.br> Message-ID: <491C6065.30809@miralink.com> GLEIZER VITOR wrote: > Hi everybody, > > > When I try to boot Nanobsd, it returns this error: > > > > > > Nov 12 20:03:53 kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > Nov 12 20:03:53 kernel: da0: Removable Direct > Access SCSI-2 device > Nov 12 20:03:53 kernel: da0: 40.000MB/s transfers > Nov 12 20:03:53 kernel: da0: 963MB (1974271 512 byte sectors: 64H 32S/T > 963C) > Nov 12 20:03:53 kernel: Trying to mount root from ufs:/dev/ad0s1a > Nov 12 20:03:53 kernel: > Nov 12 20:03:53 kernel: Manual root filesystem specification: > Nov 12 20:03:53 kernel: : Mount using filesystem > > Nov 12 20:03:53 kernel: eg. ufs:da0s1a > Nov 12 20:03:53 kernel: ? List valid disk boot devices > Nov 12 20:03:53 kernel: Abort manual input > > > > > > And manually doesn?t work, too. > > > Any idea? > > > Thanks > > > > > > Gleizer > > > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" > It appears that your "root" device is "da0" yet your nanoBSD image is trying to use the default of "ad0" for root. You should change the NANO_DRIVE variable to "da0" and rebuild your image. You could also change the file "/conf/base/etc/nanobsd.conf" to reflect "da0" as your boot device. I think that should work. -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Phone 503-621-5143 Fax 503-621-5199 MSN: sbruno@miralink.com Google: seanwbruno@gmail.com Yahoo: sean_bruno@yahoo.com From imp at bsdimp.com Thu Nov 13 14:47:21 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Nov 13 14:47:33 2008 Subject: NanoBSD boot problem In-Reply-To: <7081d84f31b719bbacd94ff7ce15675f@cedro.ufop.br> References: <7081d84f31b719bbacd94ff7ce15675f@cedro.ufop.br> Message-ID: <20081113.154700.1615465116.imp@bsdimp.com> In message: <7081d84f31b719bbacd94ff7ce15675f@cedro.ufop.br> GLEIZER VITOR writes: : Hi everybody, : : : When I try to boot Nanobsd, it returns this error: : : : ? : : : Nov 12 20:03:53? kernel: da0 at umass-sim0 bus 0 target 0 lun 0 : Nov 12 20:03:53? kernel: da0: Removable Direct : Access SCSI-2 device : Nov 12 20:03:53? kernel: da0: 40.000MB/s transfers : Nov 12 20:03:53? kernel: da0: 963MB (1974271 512 byte sectors: 64H 32S/T : 963C) : Nov 12 20:03:53? kernel: Trying to mount root from ufs:/dev/ad0s1a : Nov 12 20:03:53? kernel: : Nov 12 20:03:53? kernel: Manual root filesystem specification: : Nov 12 20:03:53? kernel: :? Mount using filesystem : : Nov 12 20:03:53? kernel: eg. ufs:da0s1a : Nov 12 20:03:53? kernel: ?????????????????? List valid disk boot devices : Nov 12 20:03:53? kernel: ?????? Abort manual input : : : ? : : : And manually doesn?t work, too. : : : Any idea? /etc/fstab has ad0s1a in it, but you have only da0? Warner From bms at incunabulum.net Sat Nov 15 06:44:54 2008 From: bms at incunabulum.net (Bruce Simpson) Date: Sat Nov 15 06:45:01 2008 Subject: MIPS port repository question Message-ID: <491EE062.2070705@incunabulum.net> Hi, Apologies for cross-post: I'm confused about which repository we should be doing active MIPS development in. Should we still be using Perforce for this? I would like to push back my changes to bfe(4) which enable it to probe and attach to the Sonics SiliconBackplane in the BCM5365P, currently these are in an SVN checkout of HEAD on my main dev box. I see gonzo@ is active on the SiBa stuff right now... go gonzo! thanks BMS From bms at incunabulum.net Sat Nov 15 07:41:31 2008 From: bms at incunabulum.net (Bruce Simpson) Date: Sat Nov 15 07:41:38 2008 Subject: ARM Jazelle support Message-ID: <491EEDA6.7040309@incunabulum.net> Bit of a long shot, just curious. Has anyone considered what it would take to implement the necessary context switch magic to support Jazelle mode in various ARM9 cores? Native Java support could be really useful, particularly so on the OpenMoko Neo, where FreeBSD is already known to run using das u-Boot: http://wiki.openmoko.org/wiki/FreeBSD thanks BMS From imp at bsdimp.com Sat Nov 15 08:59:24 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Nov 15 08:59:35 2008 Subject: ARM Jazelle support In-Reply-To: <491EEDA6.7040309@incunabulum.net> References: <491EEDA6.7040309@incunabulum.net> Message-ID: <20081115.095838.1649769600.imp@bsdimp.com> In message: <491EEDA6.7040309@incunabulum.net> Bruce Simpson writes: : Bit of a long shot, just curious. : : Has anyone considered what it would take to implement the necessary : context switch magic to support Jazelle mode in various ARM9 cores? : : Native Java support could be really useful, particularly so on the : OpenMoko Neo, where FreeBSD is already known to run using das u-Boot: : http://wiki.openmoko.org/wiki/FreeBSD When I looked at Jazelle support, the context switch stuff was well documented, but the rest of the magic needed to make it work was under NDA. Has that changed? Warner From imp at bsdimp.com Sat Nov 15 08:59:27 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Nov 15 08:59:36 2008 Subject: MIPS port repository question In-Reply-To: <491EE062.2070705@incunabulum.net> References: <491EE062.2070705@incunabulum.net> Message-ID: <20081115.100002.-1384053695.imp@bsdimp.com> In message: <491EE062.2070705@incunabulum.net> Bruce Simpson writes: : Hi, : : Apologies for cross-post: : I'm confused about which repository we should be doing active MIPS : development in. : : Should we still be using Perforce for this? : : I would like to push back my changes to bfe(4) which enable it to probe : and attach to the Sonics SiliconBackplane in the BCM5365P, currently : these are in an SVN checkout of HEAD on my main dev box. : : I see gonzo@ is active on the SiBa stuff right now... go gonzo! Most of the mips stuff has been pushed into the tree. The bleeding edge stuff is still just in p4. I didn't merge your bfe(4) changes into svn, but if you have something that's stable, there's no reason not to do so. I'd commit to p4 first, then do the normal merge, personally, but it is up to you. The next IFC will take care of merging. Warner From stas at FreeBSD.org Sat Nov 15 13:00:17 2008 From: stas at FreeBSD.org (Stanislav Sedov) Date: Sat Nov 15 13:13:39 2008 Subject: ARM Jazelle support In-Reply-To: <20081115.095838.1649769600.imp@bsdimp.com> References: <491EEDA6.7040309@incunabulum.net> <20081115.095838.1649769600.imp@bsdimp.com> Message-ID: <20081116000124.4c5adf1b.stas@FreeBSD.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 15 Nov 2008 09:58:38 -0700 (MST) "M. Warner Losh" mentioned: > > When I looked at Jazelle support, the context switch stuff was well > documented, but the rest of the magic needed to make it work was under > NDA. Has that changed? > Nope, the Jazelle technology is still closed. You'd need binary-only components from ARM Limited to utilize Jazelle. - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAkkfOKgACgkQK/VZk+smlYGDUwCdFdG37ZzS3Xv5xFOB3yULiTt2 6Z4Anil32rROcXiIUa5zop3YElpZ1zJG =UQ30 -----END PGP SIGNATURE----- From bugmaster at FreeBSD.org Mon Nov 17 03:06:49 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 17 03:07:40 2008 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200811171106.mAHB6llE082476@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/15876 embedded [picobsd] PicoBSD message of the day problems 4 problems total. From aduane at juniper.net Mon Nov 17 10:54:05 2008 From: aduane at juniper.net (Andrew Duane) Date: Mon Nov 17 10:54:12 2008 Subject: ARM Jazelle support References: <491EEDA6.7040309@incunabulum.net><20081115.095838.1649769600.imp@bsdimp.com> <20081116000124.4c5adf1b.stas@FreeBSD.org> Message-ID: <0FCFCF6165E968449991746EB91D614D0198415E@antipi.jnpr.net> Hmmm, at my last company, we had full Jazelle support for our ARM9 product, and I don't think we had any NDA agreements in place. We were using the TI OMAP chips, and we just folded Jazelle support right into our OS without any problems. If someone wants, I can contact the people involved (I didn't directly work on Jazelle, but I was in the OS group). -----Original Message----- From: owner-freebsd-embedded@freebsd.org on behalf of Stanislav Sedov Sent: Sat 11/15/2008 4:01 PM To: M. Warner Losh Cc: freebsd-embedded@freebsd.org Subject: Re: ARM Jazelle support -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 15 Nov 2008 09:58:38 -0700 (MST) "M. Warner Losh" mentioned: > > When I looked at Jazelle support, the context switch stuff was well > documented, but the rest of the magic needed to make it work was under > NDA. Has that changed? > Nope, the Jazelle technology is still closed. You'd need binary-only components from ARM Limited to utilize Jazelle. - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAkkfOKgACgkQK/VZk+smlYGDUwCdFdG37ZzS3Xv5xFOB3yULiTt2 6Z4Anil32rROcXiIUa5zop3YElpZ1zJG =UQ30 -----END PGP SIGNATURE----- _______________________________________________ freebsd-embedded@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-embedded To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" From stas at FreeBSD.org Mon Nov 17 12:08:59 2008 From: stas at FreeBSD.org (Stanislav Sedov) Date: Mon Nov 17 12:17:18 2008 Subject: ARM Jazelle support In-Reply-To: <0FCFCF6165E968449991746EB91D614D0198415E@antipi.jnpr.net> References: <491EEDA6.7040309@incunabulum.net> <20081115.095838.1649769600.imp@bsdimp.com> <20081116000124.4c5adf1b.stas@FreeBSD.org> <0FCFCF6165E968449991746EB91D614D0198415E@antipi.jnpr.net> Message-ID: <20081117231001.7efce127.stas@FreeBSD.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 17 Nov 2008 08:12:25 -0500 "Andrew Duane" mentioned: > > Hmmm, at my last company, we had full Jazelle support for our ARM9 product, and I don't think we had any NDA agreements in place. We were using the TI OMAP chips, and we just folded Jazelle support right into our OS without any problems. > > If someone wants, I can contact the people involved (I didn't directly work on Jazelle, but I was in the OS group). > That would be really nice! - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAkkhz54ACgkQK/VZk+smlYEI0QCfS1CwqM3zFf2Xrhnq3uXZoxxs NOAAn2iLMFTtgxms8MQKZ9COtkHxXaOP =dzL2 -----END PGP SIGNATURE----- From gleizzer at nti.ufop.br Tue Nov 18 08:47:34 2008 From: gleizzer at nti.ufop.br (Gleizer Vitor) Date: Tue Nov 18 08:47:41 2008 Subject: RES: NanoBSD boot problem In-Reply-To: <491C6065.30809@miralink.com> Message-ID: <20081118164733.5C8BB8FC12@mx1.freebsd.org> -----Mensagem original----- De: Sean Bruno [mailto:sbruno@miralink.com] Enviada em: quinta-feira, 13 de novembro de 2008 14:14 Para: GLEIZER VITOR Cc: freebsd-embedded@freebsd.org Assunto: Re: NanoBSD boot problem GLEIZER VITOR wrote: > Hi everybody, > > > When I try to boot Nanobsd, it returns this error: > > > > > > Nov 12 20:03:53 kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > Nov 12 20:03:53 kernel: da0: Removable Direct > Access SCSI-2 device > Nov 12 20:03:53 kernel: da0: 40.000MB/s transfers > Nov 12 20:03:53 kernel: da0: 963MB (1974271 512 byte sectors: 64H 32S/T > 963C) > Nov 12 20:03:53 kernel: Trying to mount root from ufs:/dev/ad0s1a > Nov 12 20:03:53 kernel: > Nov 12 20:03:53 kernel: Manual root filesystem specification: > Nov 12 20:03:53 kernel: : Mount using filesystem > > Nov 12 20:03:53 kernel: eg. ufs:da0s1a > Nov 12 20:03:53 kernel: ? List valid disk boot devices > Nov 12 20:03:53 kernel: Abort manual input > > > > > > And manually doesn?t work, too. > > > Any idea? > > > Thanks > > > > > > Gleizer > > > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" > It appears that your "root" device is "da0" yet your nanoBSD image is trying to use the default of "ad0" for root. You should change the NANO_DRIVE variable to "da0" and rebuild your image. You could also change the file "/conf/base/etc/nanobsd.conf" to reflect "da0" as your boot device. I think that should work. -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Phone 503-621-5143 Fax 503-621-5199 MSN: sbruno@miralink.com Google: seanwbruno@gmail.com Yahoo: sean_bruno@yahoo.com Sean, You?re right, it works now. Thanks a lot. Gleizer From bugmaster at FreeBSD.org Mon Nov 24 03:07:10 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 24 03:07:39 2008 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200811241107.mAOB79vV019854@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/15876 embedded [picobsd] PicoBSD message of the day problems 4 problems total. From salvataha1 at live.co.za Sat Nov 29 02:24:58 2008 From: salvataha1 at live.co.za (Col. Salva Taha (Rtd)) Date: Sat Nov 29 02:25:04 2008 Subject: PROPERTIES. Message-ID: <200811290914.mAT9ESqv005005@vulcan.highspd.net> Good Day, I wish to introduce myself to you.I am Col.Salva Taha a top Sudanese Goverment official who opposed the war in Dafur in my country Sudan.Due to my oppostion to the war,the goverment of my country has been persecuting me.Consequently my wife,children and I managed to enter a red cross air plane that was evacuating foreigners and we are presently in Cape Town,South Africa. We wish to invest in properties in your country with your assistance and cooperation.If you are in a good position to help my family, please send an email to the email address below indicating your desire to help my family invest the funds in your country and beyond. I urgently await your email. best regards. God bless, Col. Salva Taha (Rtd) Email:salvataha1@live.co.za