From andreast-list at fgznet.ch Sun Aug 2 20:09:52 2009 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Sun Aug 2 20:10:04 2009 Subject: No 8.0-BETA3 for ia64 & powerpc In-Reply-To: <4BB87807-BDD3-45DA-B82A-AAB05F877C4A@mac.com> References: <84BEFCFB-4E8E-4483-95D4-0D570663E3EF@mac.com> <4A7344B4.9060402@fgznet.ch> <4BB87807-BDD3-45DA-B82A-AAB05F877C4A@mac.com> Message-ID: <4A75F28B.1040708@fgznet.ch> Marcel Moolenaar wrote: > On Jul 31, 2009, at 12:23 PM, Andreas Tobler wrote: > >> Hi Marcel, >> >> Marcel Moolenaar wrote: >> >>> I'm on vacation for the next 10 days and that's right at the time >>> of BETA3 unfortunately. So there will be no BETA3 for ia64 and >>> powerpc (unless someone steps up). >>> Keep the testing going and keep reporting problems. They will all >>> be addressed in time for 8.0-RC1!!! >> Is it sufficent to build (kernel & world) and test -CURRENT svn on >> powerpc? > > Yes, definitely. Just make sure to run... > # make delete-old > # make delete-old-libs > # mergemaster -U > > ...after the install. That should cleanup some old stuff > that may prevent good testing. > BTW: A lot of libraries got their version bumped, so all > ports/packages need to be rebuilt. And here I shot myself in the toe. I did a 'portupgrade -af' afterwards and gtk link stage complained about not being able to link libcairo against libz.so.4, which I deleted with 'make delete-old-libs'. This happened on i386 and also on powerpc. I helped myself with a temporary sym link. Well, I might learn to play with the different options from portupgrade. But doing a 'portupgrade -af' before 'make delete-old-libs' should also have helped here, right? Thanks, Andreas From xcllnt at mac.com Mon Aug 3 02:09:05 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Mon Aug 3 02:09:12 2009 Subject: No 8.0-BETA3 for ia64 & powerpc In-Reply-To: <4A75F28B.1040708@fgznet.ch> References: <84BEFCFB-4E8E-4483-95D4-0D570663E3EF@mac.com> <4A7344B4.9060402@fgznet.ch> <4BB87807-BDD3-45DA-B82A-AAB05F877C4A@mac.com> <4A75F28B.1040708@fgznet.ch> Message-ID: <058B2D3C-9AAF-4BD7-B068-1993D1D71DB9@mac.com> On Aug 2, 2009, at 1:09 PM, Andreas Tobler wrote: >> Yes, definitely. Just make sure to run... >> # make delete-old >> # make delete-old-libs >> # mergemaster -U >> ...after the install. That should cleanup some old stuff >> that may prevent good testing. >> BTW: A lot of libraries got their version bumped, so all >> ports/packages need to be rebuilt. > > But doing a 'portupgrade -af' before 'make delete-old-libs' should > also have helped here, right? Ignoring possible corner case... Yes. -- Marcel Moolenaar xcllnt@mac.com From mexas at bristol.ac.uk Mon Aug 3 09:07:04 2009 From: mexas at bristol.ac.uk (Anton Shterenlikht) Date: Mon Aug 3 09:07:10 2009 Subject: No 8.0-BETA3 for ia64 & powerpc In-Reply-To: <058B2D3C-9AAF-4BD7-B068-1993D1D71DB9@mac.com> References: <84BEFCFB-4E8E-4483-95D4-0D570663E3EF@mac.com> <4A7344B4.9060402@fgznet.ch> <4BB87807-BDD3-45DA-B82A-AAB05F877C4A@mac.com> <4A75F28B.1040708@fgznet.ch> <058B2D3C-9AAF-4BD7-B068-1993D1D71DB9@mac.com> Message-ID: <20090803085041.GA20029@mech-cluster241.men.bris.ac.uk> On Sun, Aug 02, 2009 at 07:08:58PM -0700, Marcel Moolenaar wrote: > > On Aug 2, 2009, at 1:09 PM, Andreas Tobler wrote: > > >>Yes, definitely. Just make sure to run... > >> # make delete-old > >> # make delete-old-libs > >> # mergemaster -U > >>...after the install. That should cleanup some old stuff > >>that may prevent good testing. shoudn't this be documented, e.g. in section 24.7, Rebuilding "world", of the FBSD handbook? I wasn't aware of these make targets or of "-U" option. I don't think it's mentioned in the handbook. Perhaps I could've avoided some problems with system updates.. many thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 From bugmaster at FreeBSD.org Mon Aug 3 11:07:06 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 3 11:09:35 2009 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200908031107.n73B74JT088743@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 power/135576 ppc gdb cannot debug threaded programs on ppc o power/133503 ppc [sound] Sound stutter after switching ttys o power/133383 ppc firefox thr_kill crash with heavy vm load o power/133382 ppc [install] Installer gets signal 11 o power/131548 ppc ofw_syscons no longer supports 32-bit framebuffer a power/121407 ppc [panic] Won't boot up; strange error message. o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 8 problems total. From bugmaster at FreeBSD.org Mon Aug 10 11:07:03 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 10 11:09:04 2009 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200908101107.n7AB72kD025262@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 power/135576 ppc gdb cannot debug threaded programs on ppc o power/133503 ppc [sound] Sound stutter after switching ttys o power/133383 ppc firefox thr_kill crash with heavy vm load o power/133382 ppc [install] Installer gets signal 11 o power/131548 ppc ofw_syscons no longer supports 32-bit framebuffer a power/121407 ppc [panic] Won't boot up; strange error message. o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 8 problems total. From cdick at ocis.net Thu Aug 13 00:07:52 2009 From: cdick at ocis.net (Colin Dick) Date: Thu Aug 13 00:07:59 2009 Subject: Problem with ports? In-Reply-To: <1240586478.2433.2004.camel@horst-tla> References: <1240586478.2433.2004.camel@horst-tla> Message-ID: <2f15abc15701f1f47af8477f02310021@localhost> Hey all, Is anyone else having trouble with ports? I keep getting corruptions. I have tried to blow away /var/db/portsnap/ and refetch but I still get corruptions. My i386 arch machines seem to not have a problem. I have tried fetching from portsnap1.FreeBSD.org and portsnap2.FreeBSD.org: [root@web /var/db]# rm -rf portsnap [root@web /var/db]# mkdir portsnap [root@web /var/db]# chown root:wheel portsnap [root@web /var/db]# cd /usr/ports [root@web /usr/ports]# portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Fetching public key from portsnap1.FreeBSD.org... done. Fetching snapshot tag from portsnap1.FreeBSD.org... done. Fetching snapshot metadata... done. Fetching snapshot generated at Tue Aug 11 18:24:23 PDT 2009: df91fff6226ed072980a9d649807e295cfc75e7f131288100% of 58 MB 274 kBps 00m00s Extracting snapshot... done. Verifying snapshot integrity... gunzip: can't stat: snap/6642ec24a5692462dcdffb7af6d53173a8c8ebaac5c0542ccd3e5562933e3: No such file or directory snapshot corrupt. [root@web /usr/ports]# uname -a FreeBSD web.boonie.org 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Tue Feb 3 13:29:49 PST 2009 root@macmini.boonie.org:/usr/src/sys/powerpc/compile/FIREGATEEXT2 powerpc Thanks in advance for any ideas. -- Colin From axel at axel.truedestiny.net Thu Aug 13 17:52:58 2009 From: axel at axel.truedestiny.net (Axel Scheepers) Date: Thu Aug 13 17:53:08 2009 Subject: Thanks! Message-ID: <1250185976.2488.3.camel@ceridwen.thuis.net> Hi, Thanks for this; $ uname -srm FreeBSD 8.0-BETA2 powerpc $ dmesg | grep adb adb0: on pmu0 akbd0: at device 2 on adb0 ams0: at device 3 on adb0 Kind regards, Axel Scheepers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20090813/76d78663/attachment.pgp From tinderbox at freebsd.org Fri Aug 14 06:31:40 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Fri Aug 14 06:31:47 2009 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20090814063137.B39877302F@freebsd-current.sentex.ca> TB --- 2009-08-14 05:09:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-08-14 05:09:00 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-08-14 05:09:00 - cleaning the object tree TB --- 2009-08-14 05:09:34 - cvsupping the source tree TB --- 2009-08-14 05:09:34 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-08-14 05:09:43 - building world TB --- 2009-08-14 05:09:43 - MAKEOBJDIRPREFIX=/obj TB --- 2009-08-14 05:09:43 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-08-14 05:09:43 - TARGET=powerpc TB --- 2009-08-14 05:09:43 - TARGET_ARCH=powerpc TB --- 2009-08-14 05:09:43 - TZ=UTC TB --- 2009-08-14 05:09:43 - __MAKE_CONF=/dev/null TB --- 2009-08-14 05:09:43 - cd /src TB --- 2009-08-14 05:09:43 - /usr/bin/make -B buildworld >>> World build started on Fri Aug 14 05:09:45 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] ===> usr.sbin/mfiutil (all) cc -O2 -pipe -fno-builtin-strftime -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/mfiutil/mfiutil.c cc -O2 -pipe -fno-builtin-strftime -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/mfiutil/mfi_cmd.c cc -O2 -pipe -fno-builtin-strftime -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/mfiutil/mfi_config.c cc -O2 -pipe -fno-builtin-strftime -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/mfiutil/mfi_drive.c cc1: warnings being treated as errors /src/usr.sbin/mfiutil/mfi_drive.c: In function 'mfi_lookup_drive': /src/usr.sbin/mfiutil/mfi_drive.c:120: warning: comparison between signed and unsigned *** Error code 1 Stop in /src/usr.sbin/mfiutil. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-08-14 06:31:37 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-08-14 06:31:37 - ERROR: failed to build world TB --- 2009-08-14 06:31:37 - 3896.80 user 364.78 system 4957.45 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From bugmaster at FreeBSD.org Mon Aug 17 11:07:01 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 17 11:09:24 2009 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200908171107.n7HB70m4075902@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 power/135576 ppc gdb cannot debug threaded programs on ppc o power/133503 ppc [sound] Sound stutter after switching ttys o power/133383 ppc firefox thr_kill crash with heavy vm load o power/133382 ppc [install] Installer gets signal 11 o power/131548 ppc ofw_syscons no longer supports 32-bit framebuffer a power/121407 ppc [panic] Won't boot up; strange error message. o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 8 problems total. From tinderbox at freebsd.org Wed Aug 19 14:05:38 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Aug 19 14:06:53 2009 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <200908191405.n7JE57ZB001169@freebsd-current2.sentex.ca> TB --- 2009-08-19 14:05:01 - tinderbox 2.6 running on freebsd-current2.sentex.ca TB --- 2009-08-19 14:05:01 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-08-19 14:05:01 - cleaning the object tree TB --- 2009-08-19 14:05:01 - checking out /src from http://svn.freebsd.org/base/ TB --- 2009-08-19 14:05:01 - cd /tinderbox/HEAD/powerpc/powerpc TB --- 2009-08-19 14:05:02 - /usr/local/bin/svn update /src TB --- 2009-08-19 14:05:02 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2009-08-19 14:05:02 - ERROR: unable to check out the source tree TB --- 2009-08-19 14:05:02 - 0.03 user 0.01 system 0.06 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From axel.scheepers at nl.clara.net Wed Aug 19 16:55:07 2009 From: axel.scheepers at nl.clara.net (Axel Scheepers) Date: Wed Aug 19 16:55:13 2009 Subject: auto booting Message-ID: <1250699898.21000.37.camel@ceridwen.thuis.net> Hi List, First of all thanks for porting FreeBSD to powerpc, it runs great on my iBook over here and now I can even use my adb keyboard. Thanks! When installing I created an !Apple_HFS partition which I formatted and labeled Boot with hfsutils from ports yesterday so I can copy the loader there and don't have to boot from cd each time. This works great without auto boot; boot hd:loader hd:4 works like a charm. When I had OpenBSD on this laptop I remember I could just set boot-device to be able to autoboot but when I try this it seems the kernel is loading (I can hear it accessing drives/cdrom and the host starts pinging after a while) but there's no video output except for the basic moire x like background from openfirmware. The laptop also doesn't boot all the way when I use this, even after waiting quite some time there was no sshd listening so I rebooted it and booted it manually which works fine. NetBSD also has this issue if I'm correct, can someone explain to me why this is happening? Thanks, Kind regards, Axel Scheepers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20090819/c6bd0f78/attachment.pgp From nwhitehorn at freebsd.org Wed Aug 19 19:08:23 2009 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Wed Aug 19 19:08:29 2009 Subject: auto booting In-Reply-To: <1250699898.21000.37.camel@ceridwen.thuis.net> References: <1250699898.21000.37.camel@ceridwen.thuis.net> Message-ID: On Wed, 19 Aug 2009, Axel Scheepers wrote: > Hi List, > > First of all thanks for porting FreeBSD to powerpc, it runs great on my > iBook over here and now I can even use my adb keyboard. Thanks! > > When installing I created an !Apple_HFS partition which I formatted and > labeled Boot with hfsutils from ports yesterday so I can copy the loader > there and don't have to boot from cd each time. This works great without > auto boot; boot hd:loader hd:4 works like a charm. > > When I had OpenBSD on this laptop I remember I could just set > boot-device to be able to autoboot but when I try this it seems the > kernel is loading (I can hear it accessing drives/cdrom and the host > starts pinging after a while) but there's no video output except for the > basic moire x like background from openfirmware. The laptop also doesn't > boot all the way when I use this, even after waiting quite some time > there was no sshd listening so I rebooted it and booted it manually > which works fine. > > NetBSD also has this issue if I'm correct, can someone explain to me why > this is happening? Open Firmware needs its output set to screen in order to initialize the display. You can do this with a custom bootscript, or you can use the HFS loader image that the system provides at /boot/boot1.hfs. This is a small HFS filesystem containing a boot block and an OF script that you can dd to a !Apple_HFS or !Apple_Bootstrap partition. sysinstall still needs to be taught about this... -Nathan From axel.scheepers at nl.clara.net Wed Aug 19 20:17:47 2009 From: axel.scheepers at nl.clara.net (Axel Scheepers) Date: Wed Aug 19 20:17:59 2009 Subject: auto booting In-Reply-To: References: <1250699898.21000.37.camel@ceridwen.thuis.net> Message-ID: <1250713035.21000.49.camel@ceridwen.thuis.net> On Wed, 2009-08-19 at 14:08 -0500, Nathan Whitehorn wrote: > Open Firmware needs its output set to screen in order to initialize the > display. You can do this with a custom bootscript, or you can use the HFS > loader image that the system provides at /boot/boot1.hfs. This is a > small HFS filesystem containing a boot block and an OF script that you can > dd to a !Apple_HFS or !Apple_Bootstrap partition. sysinstall still needs > to be taught about this... > -Nathan Thanks Nathan, I'll check this out next time I'm near my iBook. Kind regards, Axel Scheepers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20090819/4dd2962f/attachment.pgp From xcllnt at mac.com Sun Aug 23 17:35:48 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Sun Aug 23 17:35:54 2009 Subject: 8.0-BETA3 *is* available [was: No 8.0-BETA3 for ia64 & powerpc] In-Reply-To: <84BEFCFB-4E8E-4483-95D4-0D570663E3EF@mac.com> References: <84BEFCFB-4E8E-4483-95D4-0D570663E3EF@mac.com> Message-ID: On Jul 31, 2009, at 11:10 AM, Marcel Moolenaar wrote: > I'm on vacation for the next 10 days and that's right at the time > of BETA3 unfortunately. So there will be no BETA3 for ia64 and > powerpc (unless someone steps up). 8.0-BETA3 got delayed until after my vacation, so I made them. Look for them on your favorite mirror! FYI, -- Marcel Moolenaar xcllnt@mac.com From bugmaster at FreeBSD.org Mon Aug 24 11:07:02 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 24 11:09:08 2009 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200908241107.n7OB71wK048689@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 power/135576 ppc gdb cannot debug threaded programs on ppc o power/133503 ppc [sound] Sound stutter after switching ttys o power/133383 ppc firefox thr_kill crash with heavy vm load o power/133382 ppc [install] Installer gets signal 11 o power/131548 ppc ofw_syscons no longer supports 32-bit framebuffer a power/121407 ppc [panic] Won't boot up; strange error message. o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 8 problems total. From axel at axel.truedestiny.net Mon Aug 24 16:38:22 2009 From: axel at axel.truedestiny.net (Axel Scheepers) Date: Mon Aug 24 16:38:30 2009 Subject: Turn off backlight on iBook Message-ID: <1251131900.42823.38.camel@ceridwen.thuis.net> Hi List, Sorry for asking but I can't seem to find where and how I can turn off the backlight for my iBook, is this possible with FreeBSD? Thanks, Kind regards, Axel Scheepers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20090824/0603732e/attachment.pgp From nse at delfi-konsult.com Wed Aug 26 10:48:08 2009 From: nse at delfi-konsult.com (Niels S. Eliasen) Date: Wed Aug 26 10:48:15 2009 Subject: gjournal on gmirror..... Message-ID: <813C88C5-70D6-4B1B-AD4B-7EE55AD68F52@delfi-konsult.com> hi guys is there a cookbook somewhere for getting gjournal running a gmirror setup ?? Having burnt myself pretty badly on such a setup... I would like to find something... or someone ....who has done this previously... in order not to burn myself in the future ;-) While we are at the worst-case scenario anyhow..... ... How do I build a rescue cd .?? as there is no rescue-disk for macppc .... kind regards nse "Ach, crivens, what a wee snotter....." Quote from "The Wee Free Men" by Terry Pratchett From Daan at vehosting.nl Fri Aug 28 19:27:30 2009 From: Daan at vehosting.nl (Daan Vreeken) Date: Fri Aug 28 19:27:38 2009 Subject: FreeBSD/powerpc on MPC5200 In-Reply-To: References: <35914876-0CFF-427B-8F80-B1BEEA5A7A18@semihalf.com> <20090523172128.2e0a3f2b@fubar.geek.nz> Message-ID: <200908282127.28482.Daan@vehosting.nl> Hi Rafal (and the list), On Sunday 24 May 2009 21:15:44 Rafal Jaworowski wrote: > On 2009-05-23, at 07:21, Andrew Turner wrote: > > On Fri, 22 May 2009 12:21:01 +0200 > > > > Rafal Jaworowski wrote: > >> On 2009-05-11, at 15:15, Peter Czanik wrote: > >>> Rafal Jaworowski ?rta: > >>>> I'd like to let people know that FreeBSD/powerpc is now able to > >>>> boot into single user on the Freescale MPC5200 system-on-chip > >>>> (EFIKA board). The environment is very simplistic: RAM disk based > >>>> root fs, as > >>>> there's no peripherals drivers besides serial console and the > >>>> built- in > >>>> PIC. See this log: http://people.freebsd.org/~raj/logs/efika.log > >>> > >>> Wow, great news! Two questions: > >>> - are there any plans to support additional devices? > >> > >> We don't have immediate plans for other devices drivers, but this > >> basic support will be merged into SVN, and it would be greatly > >> welcome to see people help with remaining items. > > > > Is there a patch available? I would like to get back to working on the > > EFIKA. > > Preliminary diff against 2009.04.06 HEAD is here: > http://people.freebsd.org/~raj/patches/powerpc/efika.diff > > Comments or questions welcome. Some bits need to be streamlined so > that all AIM/OF variations work together, and the code has to be > rebased against up-to-date HEAD. I have downloaded your diff and succesfully patched it to -HEAD (checked out on 2009-08-25). Right now I'm looking into getting the USB controller working. (That would allow me to use network & disks all in one go.) I have written the OHCI attachment code (inspired by a mix of Warner's atmel version, mpc5xxx/ic.c and uart_dev_psc.c) and gotten it to succesfully attach to the OHCI controller when booting the Efika board. USB is not (yet) working correctly. Near the end of ohci_init(), the board seems to halt completely for about 30 seconds and after that, the OHCI controller sets the 'unrecoverable error' flag. A complete dmesg dump can be found here : http://vehosting.nl/pub_diffs/efika-daan-2009-08-28-ohci_attaching_but_failing.txt The kernel that produced this can be downloaded here : http://vehosting.nl/pub_diffs/efika-daan-2009-08-28-ohci_attaching_but_failing.kernel The files I added/changed to get the attachment of the OHCI controller to 'work' can be found here : http://vehosting.nl/pub_diffs/efika-daan-2009-08-28_changed_files.tar.gz (Warning : Ugly! and full of printf's for now!) (I could have missed one, let me know if you can't get it to work.) The above dmesg shows a number of printf's I've added to ohci.c . My mutilated version can be found here : http://vehosting.nl/pub_diffs/efika-daan-2009-08-28_ohci.c As you can see, I printf() the interrupt status register at various points during ohci_init(). The 'unrecoverable error' flag gets set just a couple of miliseconds after the following command has been executed : /* And finally start it! */ OWRITE4(sc, OHCI_CONTROL, ctl); After that OWRITE4(), the board sits for about 30 seconds and then continues. I'm just guessing what's going on here, but could it be that (one of?) the endpoint lists isn't properly setup and that the OHCI controller keeps the CPU from accessing memory while it's racing through memory following corrupt/invalid 'next' pointers? Regards, -- Daan Vreeken VEHosting http://VEHosting.nl tel: +31-(0)40-7113050 / +31-(0)6-46210825 KvK nr: 17174380 From hselasky at c2i.net Fri Aug 28 20:46:16 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Aug 28 20:46:24 2009 Subject: FreeBSD/powerpc on MPC5200 In-Reply-To: <200908282127.28482.Daan@vehosting.nl> References: <35914876-0CFF-427B-8F80-B1BEEA5A7A18@semihalf.com> <200908282127.28482.Daan@vehosting.nl> Message-ID: <200908282146.28715.hselasky@c2i.net> On Friday 28 August 2009 21:27:28 Daan Vreeken wrote: > Hi Rafal (and the list), > > On Sunday 24 May 2009 21:15:44 Rafal Jaworowski wrote: > > On 2009-05-23, at 07:21, Andrew Turner wrote: > > > On Fri, 22 May 2009 12:21:01 +0200 > > > > > > Rafal Jaworowski wrote: > > >> On 2009-05-11, at 15:15, Peter Czanik wrote: > > >>> Rafal Jaworowski ?rta: > > >>>> I'd like to let people know that FreeBSD/powerpc is now able to > > >>>> boot into single user on the Freescale MPC5200 system-on-chip > > >>>> (EFIKA board). The environment is very simplistic: RAM disk based > > >>>> root fs, as > > >>>> there's no peripherals drivers besides serial console and the > > >>>> built- in > > >>>> PIC. See this log: http://people.freebsd.org/~raj/logs/efika.log > > >>> > > >>> Wow, great news! Two questions: > > >>> - are there any plans to support additional devices? > > >> > > >> We don't have immediate plans for other devices drivers, but this > > >> basic support will be merged into SVN, and it would be greatly > > >> welcome to see people help with remaining items. > > > > > > Is there a patch available? I would like to get back to working on the > > > EFIKA. > > > > Preliminary diff against 2009.04.06 HEAD is here: > > http://people.freebsd.org/~raj/patches/powerpc/efika.diff > > > > Comments or questions welcome. Some bits need to be streamlined so > > that all AIM/OF variations work together, and the code has to be > > rebased against up-to-date HEAD. > > I have downloaded your diff and succesfully patched it to -HEAD (checked > out on 2009-08-25). > Right now I'm looking into getting the USB controller working. (That would > allow me to use network & disks all in one go.) > > I have written the OHCI attachment code (inspired by a mix of Warner's > atmel version, mpc5xxx/ic.c and uart_dev_psc.c) and gotten it to > succesfully attach to the OHCI controller when booting the Efika board. > USB is not (yet) working correctly. Near the end of ohci_init(), the board > seems to halt completely for about 30 seconds and after that, the OHCI > controller sets the 'unrecoverable error' flag. > > A complete dmesg dump can be found here : > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28-ohci_attaching_but_fail >ing.txt The kernel that produced this can be downloaded here : > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28-ohci_attaching_but_fail >ing.kernel > > The files I added/changed to get the attachment of the OHCI controller > to 'work' can be found here : > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28_changed_files.tar.gz > (Warning : Ugly! and full of printf's for now!) > (I could have missed one, let me know if you can't get it to work.) > > The above dmesg shows a number of printf's I've added to ohci.c . My > mutilated version can be found here : > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28_ohci.c > > As you can see, I printf() the interrupt status register at various points > during ohci_init(). The 'unrecoverable error' flag gets set just a couple > of miliseconds after the following command has been executed : > > /* And finally start it! */ > OWRITE4(sc, OHCI_CONTROL, ctl); > > After that OWRITE4(), the board sits for about 30 seconds and then > continues. I'm just guessing what's going on here, but could it be that > (one of?) the endpoint lists isn't properly setup and that the OHCI > controller keeps the CPU from accessing memory while it's racing through > memory following corrupt/invalid 'next' pointers? Maybe busdma is not computing correct physical addresses for the kernel virtual memory loaded into DMA. --HPS From Daan at vehosting.nl Sat Aug 29 00:25:59 2009 From: Daan at vehosting.nl (Daan Vreeken) Date: Sat Aug 29 00:26:08 2009 Subject: FreeBSD/powerpc on MPC5200 In-Reply-To: <200908282146.28715.hselasky@c2i.net> References: <35914876-0CFF-427B-8F80-B1BEEA5A7A18@semihalf.com> <200908282127.28482.Daan@vehosting.nl> <200908282146.28715.hselasky@c2i.net> Message-ID: <200908290225.59094.Daan@vehosting.nl> Hi, On Friday 28 August 2009 21:46:27 Hans Petter Selasky wrote: > On Friday 28 August 2009 21:27:28 Daan Vreeken wrote: > > Hi Rafal (and the list), > > > > On Sunday 24 May 2009 21:15:44 Rafal Jaworowski wrote: > > > On 2009-05-23, at 07:21, Andrew Turner wrote: > > > > On Fri, 22 May 2009 12:21:01 +0200 > > > > > > > > Rafal Jaworowski wrote: > > > >> On 2009-05-11, at 15:15, Peter Czanik wrote: > > > >>> Rafal Jaworowski ?rta: > > > >>>> I'd like to let people know that FreeBSD/powerpc is now able to > > > >>>> boot into single user on the Freescale MPC5200 system-on-chip > > > >>>> (EFIKA board). The environment is very simplistic: RAM disk based > > > >>>> root fs, as > > > >>>> there's no peripherals drivers besides serial console and the > > > >>>> built- in > > > >>>> PIC. See this log: http://people.freebsd.org/~raj/logs/efika.log > > > >>> > > > >>> Wow, great news! Two questions: > > > >>> - are there any plans to support additional devices? > > > >> > > > >> We don't have immediate plans for other devices drivers, but this > > > >> basic support will be merged into SVN, and it would be greatly > > > >> welcome to see people help with remaining items. > > > > > > > > Is there a patch available? I would like to get back to working on > > > > the EFIKA. > > > > > > Preliminary diff against 2009.04.06 HEAD is here: > > > http://people.freebsd.org/~raj/patches/powerpc/efika.diff > > > > > > Comments or questions welcome. Some bits need to be streamlined so > > > that all AIM/OF variations work together, and the code has to be > > > rebased against up-to-date HEAD. > > > > I have downloaded your diff and succesfully patched it to -HEAD (checked > > out on 2009-08-25). > > Right now I'm looking into getting the USB controller working. (That > > would allow me to use network & disks all in one go.) > > > > I have written the OHCI attachment code (inspired by a mix of Warner's > > atmel version, mpc5xxx/ic.c and uart_dev_psc.c) and gotten it to > > succesfully attach to the OHCI controller when booting the Efika board. > > USB is not (yet) working correctly. Near the end of ohci_init(), the > > board seems to halt completely for about 30 seconds and after that, the > > OHCI controller sets the 'unrecoverable error' flag. > > > > A complete dmesg dump can be found here : > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28-ohci_attaching_but_fa > >il ing.txt The kernel that produced this can be downloaded here : > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28-ohci_attaching_but_fa > >il ing.kernel > > > > The files I added/changed to get the attachment of the OHCI controller > > to 'work' can be found here : > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28_changed_files.tar.gz > > (Warning : Ugly! and full of printf's for now!) > > (I could have missed one, let me know if you can't get it to work.) > > > > The above dmesg shows a number of printf's I've added to ohci.c . My > > mutilated version can be found here : > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28_ohci.c > > > > As you can see, I printf() the interrupt status register at various > > points during ohci_init(). The 'unrecoverable error' flag gets set just a > > couple of miliseconds after the following command has been executed : > > > > /* And finally start it! */ > > OWRITE4(sc, OHCI_CONTROL, ctl); > > > > After that OWRITE4(), the board sits for about 30 seconds and then > > continues. I'm just guessing what's going on here, but could it be that > > (one of?) the endpoint lists isn't properly setup and that the OHCI > > controller keeps the CPU from accessing memory while it's racing through > > memory following corrupt/invalid 'next' pointers? > > Maybe busdma is not computing correct physical addresses for the kernel > virtual memory loaded into DMA. Sounds plausible. ohci_dumpregs() shows the following : ohci_dumpregs:584: ohci_dumpregs: rev=0x00000010 control=0x000000bf command=0x00000000 ohci_dumpregs:588: intrstat=0x00000054 intre=0x8000005a intrd=0x8000005a ohci_dumpregs:592: hcca=0x01c12a00 percur=0x0017c500 ctrlhd=0x01c20880 ohci_dumpregs:596: ctrlcur=0x00000000 bulkhd=0x01c20800 bulkcur=0x00000000 ohci_dumpregs:600: done=0x00000000 fmival=0xa7782edf fmrem=0x8000151b ohci_dumpregs:604: fmnum=0x0000fe72 perst=0x00002a2f lsthrs=0x00000628 ohci_dumpregs:608: desca=0x02001202 descb=0x00000000 stat=0x00000000 ohci_dumpregs:611: port1=0x00010301 port2=0x00010101 ohci_dumpregs:617: HCCA: frame_number=0x35fe0000 done_head=0x00000000 In ohci_init() I've added a printf() directly after the following two lines : usbd_get_page(&sc->sc_hw.hcca_pc, 0, &buf_res); sc->sc_hcca_p = buf_res.buffer; that prints the virtual and physical address of the HCCA : printf("hcca: buf_res.buffer=%p, buf_res.physaddr=%x\n", buf_res.buffer, buf_res.physaddr); This gives the following line in the dmesg output : hcca: buf_res.buffer=0x1c12a00, buf_res.physaddr=1c12a00 I'm not a powerpc VM guru, but it looks as if the virtual and physical address are the same. Are they mapped 1:1 or is there something going wrong? Anyone? Regards -- Daan Vreeken VEHosting http://VEHosting.nl tel: +31-(0)40-7113050 / +31-(0)6-46210825 KvK nr: 17174380 From Daan at vehosting.nl Sun Aug 30 13:49:19 2009 From: Daan at vehosting.nl (Daan Vreeken) Date: Sun Aug 30 13:49:27 2009 Subject: FreeBSD/powerpc on MPC5200 In-Reply-To: <200908282146.28715.hselasky@c2i.net> References: <35914876-0CFF-427B-8F80-B1BEEA5A7A18@semihalf.com> <200908282127.28482.Daan@vehosting.nl> <200908282146.28715.hselasky@c2i.net> Message-ID: <200908301549.18407.Daan@vehosting.nl> Hi Hans Petter, On Friday 28 August 2009 21:46:27 Hans Petter Selasky wrote: > On Friday 28 August 2009 21:27:28 Daan Vreeken wrote: > > Hi Rafal (and the list), > > > > On Sunday 24 May 2009 21:15:44 Rafal Jaworowski wrote: > > > On 2009-05-23, at 07:21, Andrew Turner wrote: > > > > On Fri, 22 May 2009 12:21:01 +0200 > > > > > > > > Rafal Jaworowski wrote: > > > >> On 2009-05-11, at 15:15, Peter Czanik wrote: > > > >>> Rafal Jaworowski ?rta: > > > >>>> I'd like to let people know that FreeBSD/powerpc is now able to > > > >>>> boot into single user on the Freescale MPC5200 system-on-chip > > > >>>> (EFIKA board). The environment is very simplistic: RAM disk based > > > >>>> root fs, as > > > >>>> there's no peripherals drivers besides serial console and the > > > >>>> built- in > > > >>>> PIC. See this log: http://people.freebsd.org/~raj/logs/efika.log > > > >>> > > > >>> Wow, great news! Two questions: > > > >>> - are there any plans to support additional devices? > > > >> > > > >> We don't have immediate plans for other devices drivers, but this > > > >> basic support will be merged into SVN, and it would be greatly > > > >> welcome to see people help with remaining items. > > > > > > > > Is there a patch available? I would like to get back to working on > > > > the EFIKA. > > > > > > Preliminary diff against 2009.04.06 HEAD is here: > > > http://people.freebsd.org/~raj/patches/powerpc/efika.diff > > > > > > Comments or questions welcome. Some bits need to be streamlined so > > > that all AIM/OF variations work together, and the code has to be > > > rebased against up-to-date HEAD. > > > > I have downloaded your diff and succesfully patched it to -HEAD (checked > > out on 2009-08-25). > > Right now I'm looking into getting the USB controller working. (That > > would allow me to use network & disks all in one go.) > > > > I have written the OHCI attachment code (inspired by a mix of Warner's > > atmel version, mpc5xxx/ic.c and uart_dev_psc.c) and gotten it to > > succesfully attach to the OHCI controller when booting the Efika board. > > USB is not (yet) working correctly. Near the end of ohci_init(), the > > board seems to halt completely for about 30 seconds and after that, the > > OHCI controller sets the 'unrecoverable error' flag. > > > > A complete dmesg dump can be found here : > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28-ohci_attaching_but_fa > >il ing.txt The kernel that produced this can be downloaded here : > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28-ohci_attaching_but_fa > >il ing.kernel > > > > The files I added/changed to get the attachment of the OHCI controller > > to 'work' can be found here : > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28_changed_files.tar.gz > > (Warning : Ugly! and full of printf's for now!) > > (I could have missed one, let me know if you can't get it to work.) > > > > The above dmesg shows a number of printf's I've added to ohci.c . My > > mutilated version can be found here : > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28_ohci.c > > > > As you can see, I printf() the interrupt status register at various > > points during ohci_init(). The 'unrecoverable error' flag gets set just a > > couple of miliseconds after the following command has been executed : > > > > /* And finally start it! */ > > OWRITE4(sc, OHCI_CONTROL, ctl); > > > > After that OWRITE4(), the board sits for about 30 seconds and then > > continues. I'm just guessing what's going on here, but could it be that > > (one of?) the endpoint lists isn't properly setup and that the OHCI > > controller keeps the CPU from accessing memory while it's racing through > > memory following corrupt/invalid 'next' pointers? > > Maybe busdma is not computing correct physical addresses for the kernel > virtual memory loaded into DMA. I've looking closely at the logs I generated earlier and this doesn't seem to be the case (I think). The physical address of the HCCA (Host Controller Communications Area) looks the same and the frame_number counter is advancing in this memory area as soon as the controller is enabled. One thing that strikes me is the value of the frame number though : ohci_dumpregs:599: ohci_dumpregs: rev=0x00000010 control=0x00000093 command=0x00000002 ohci_dumpregs:603: intrstat=0x00000040 intre=0x8000005a intrd=0x8000005a ohci_dumpregs:607: hcca=0x01c12a00 percur=0x48000060 ctrlhd=0x01c20880 ohci_dumpregs:611: ctrlcur=0x00000000 bulkhd=0x01c20800 bulkcur=0x00000000 ohci_dumpregs:615: done=0x00000000 fmival=0xa7782edf fmrem=0x800025e7 ohci_dumpregs:619: fmnum=0x000000e5 perst=0x00002a2f lsthrs=0x00000628 ohci_dumpregs:623: desca=0x02001202 descb=0x00000000 stat=0x00000000 ohci_dumpregs:626: port1=0x00100303 port2=0x00010101 ohci_dumpregs:632: HCCA: frame_number=0x35fe0000 done_head=0x00000000 The frame number at this particular moment is '0x35fe0000', though the OHCI spec says it should be a 16 bit counter, followed by 16 bits of padding (that should read back as '0'). Could it be a big-endian controller, while the USB code expects little-endian? -- Daan Vreeken VEHosting http://VEHosting.nl tel: +31-(0)40-7113050 / +31-(0)6-46210825 KvK nr: 17174380 From Daan at vehosting.nl Sun Aug 30 14:14:57 2009 From: Daan at vehosting.nl (Daan Vreeken) Date: Sun Aug 30 14:15:04 2009 Subject: FreeBSD/powerpc on MPC5200 In-Reply-To: <200908301549.18407.Daan@vehosting.nl> References: <35914876-0CFF-427B-8F80-B1BEEA5A7A18@semihalf.com> <200908282146.28715.hselasky@c2i.net> <200908301549.18407.Daan@vehosting.nl> Message-ID: <200908301614.58264.Daan@vehosting.nl> On Sunday 30 August 2009 15:49:17 Daan Vreeken wrote: > Hi Hans Petter, > > On Friday 28 August 2009 21:46:27 Hans Petter Selasky wrote: > > On Friday 28 August 2009 21:27:28 Daan Vreeken wrote: > > > Hi Rafal (and the list), > > > > > > On Sunday 24 May 2009 21:15:44 Rafal Jaworowski wrote: > > > > On 2009-05-23, at 07:21, Andrew Turner wrote: > > > > > On Fri, 22 May 2009 12:21:01 +0200 > > > > > > > > > > Rafal Jaworowski wrote: > > > > >> On 2009-05-11, at 15:15, Peter Czanik wrote: > > > > >>> Rafal Jaworowski ?rta: > > > > >>>> I'd like to let people know that FreeBSD/powerpc is now able to > > > > >>>> boot into single user on the Freescale MPC5200 system-on-chip > > > > >>>> (EFIKA board). The environment is very simplistic: RAM disk > > > > >>>> based root fs, as > > > > >>>> there's no peripherals drivers besides serial console and the > > > > >>>> built- in > > > > >>>> PIC. See this log: http://people.freebsd.org/~raj/logs/efika.log > > > > >>> > > > > >>> Wow, great news! Two questions: > > > > >>> - are there any plans to support additional devices? > > > > >> > > > > >> We don't have immediate plans for other devices drivers, but this > > > > >> basic support will be merged into SVN, and it would be greatly > > > > >> welcome to see people help with remaining items. > > > > > > > > > > Is there a patch available? I would like to get back to working on > > > > > the EFIKA. > > > > > > > > Preliminary diff against 2009.04.06 HEAD is here: > > > > http://people.freebsd.org/~raj/patches/powerpc/efika.diff > > > > > > > > Comments or questions welcome. Some bits need to be streamlined so > > > > that all AIM/OF variations work together, and the code has to be > > > > rebased against up-to-date HEAD. > > > > > > I have downloaded your diff and succesfully patched it to -HEAD > > > (checked out on 2009-08-25). > > > Right now I'm looking into getting the USB controller working. (That > > > would allow me to use network & disks all in one go.) > > > > > > I have written the OHCI attachment code (inspired by a mix of Warner's > > > atmel version, mpc5xxx/ic.c and uart_dev_psc.c) and gotten it to > > > succesfully attach to the OHCI controller when booting the Efika board. > > > USB is not (yet) working correctly. Near the end of ohci_init(), the > > > board seems to halt completely for about 30 seconds and after that, the > > > OHCI controller sets the 'unrecoverable error' flag. > > > > > > A complete dmesg dump can be found here : > > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28-ohci_attaching_but_ > > >fa il ing.txt The kernel that produced this can be downloaded here : > > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28-ohci_attaching_but_ > > >fa il ing.kernel > > > > > > The files I added/changed to get the attachment of the OHCI controller > > > to 'work' can be found here : > > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28_changed_files.tar.g > > >z (Warning : Ugly! and full of printf's for now!) > > > (I could have missed one, let me know if you can't get it to work.) > > > > > > The above dmesg shows a number of printf's I've added to ohci.c . My > > > mutilated version can be found here : > > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28_ohci.c > > > > > > As you can see, I printf() the interrupt status register at various > > > points during ohci_init(). The 'unrecoverable error' flag gets set just > > > a couple of miliseconds after the following command has been executed : > > > > > > /* And finally start it! */ > > > OWRITE4(sc, OHCI_CONTROL, ctl); > > > > > > After that OWRITE4(), the board sits for about 30 seconds and then > > > continues. I'm just guessing what's going on here, but could it be that > > > (one of?) the endpoint lists isn't properly setup and that the OHCI > > > controller keeps the CPU from accessing memory while it's racing > > > through memory following corrupt/invalid 'next' pointers? > > > > Maybe busdma is not computing correct physical addresses for the kernel > > virtual memory loaded into DMA. > > I've looking closely at the logs I generated earlier and this doesn't seem > to be the case (I think). The physical address of the HCCA (Host Controller > Communications Area) looks the same and the frame_number counter is > advancing in this memory area as soon as the controller is enabled. > One thing that strikes me is the value of the frame number though : > > ohci_dumpregs:599: ohci_dumpregs: rev=0x00000010 control=0x00000093 > command=0x00000002 > ohci_dumpregs:603: intrstat=0x00000040 intre=0x8000005a intrd=0x8000005a > ohci_dumpregs:607: hcca=0x01c12a00 percur=0x48000060 ctrlhd=0x01c20880 > ohci_dumpregs:611: ctrlcur=0x00000000 bulkhd=0x01c20800 bulkcur=0x00000000 > ohci_dumpregs:615: done=0x00000000 fmival=0xa7782edf fmrem=0x800025e7 > ohci_dumpregs:619: fmnum=0x000000e5 perst=0x00002a2f lsthrs=0x00000628 > ohci_dumpregs:623: desca=0x02001202 descb=0x00000000 stat=0x00000000 > ohci_dumpregs:626: port1=0x00100303 port2=0x00010101 > ohci_dumpregs:632: HCCA: frame_number=0x35fe0000 done_head=0x00000000 > > The frame number at this particular moment is '0x35fe0000', though the OHCI > spec says it should be a 16 bit counter, followed by 16 bits of padding > (that should read back as '0'). > > Could it be a big-endian controller, while the USB code expects > little-endian? Yes, that was it. Changing every 'htole32' into 'htobe32' and every 'le32toh' into 'be32toh' in sys/dev/usb/controller/ohci.c gets the USB controller to work : ... Timecounter "decrementer" frequency 33000000 Hz quality 0 Timecounters tick every 10.000 msec usbus0: 12Mbps Full Speed USB v1.0 Root mount waiting for: usbus0 ugen0.1: at usbus0 uhub0: on usbus0 uhub0: 2 ports with 2 removable, self powered Root mount waiting for: usbus0 ugen0.2: at usbus0 Root mount waiting for: usbus0 ugen0.3: at usbus0 (For those with an Efika board, here's a working kernel : http://vehosting.nl/pub_diffs/efika-daan-2009-08-30-usb-working.kernel ) -- Daan Vreeken VEHosting http://VEHosting.nl tel: +31-(0)40-7113050 / +31-(0)6-46210825 KvK nr: 17174380 From Daan at vehosting.nl Sun Aug 30 15:53:23 2009 From: Daan at vehosting.nl (Daan Vreeken) Date: Sun Aug 30 15:53:30 2009 Subject: FreeBSD/powerpc on MPC5200 In-Reply-To: <200908301614.58264.Daan@vehosting.nl> References: <35914876-0CFF-427B-8F80-B1BEEA5A7A18@semihalf.com> <200908301549.18407.Daan@vehosting.nl> <200908301614.58264.Daan@vehosting.nl> Message-ID: <200908301753.24288.Daan@vehosting.nl> Hi Hans Petter, On Sunday 30 August 2009 16:14:57 Daan Vreeken wrote: > On Sunday 30 August 2009 15:49:17 Daan Vreeken wrote: > > On Friday 28 August 2009 21:46:27 Hans Petter Selasky wrote: > > > On Friday 28 August 2009 21:27:28 Daan Vreeken wrote: > > > > Hi Rafal (and the list), > > > > > > > > On Sunday 24 May 2009 21:15:44 Rafal Jaworowski wrote: > > > > > On 2009-05-23, at 07:21, Andrew Turner wrote: > > > > > > On Fri, 22 May 2009 12:21:01 +0200 > > > > > > > > > > > > Rafal Jaworowski wrote: > > > > > >> On 2009-05-11, at 15:15, Peter Czanik wrote: > > > > > >>> Rafal Jaworowski ?rta: > > > > > >>>> I'd like to let people know that FreeBSD/powerpc is now able > > > > > >>>> to boot into single user on the Freescale MPC5200 > > > > > >>>> system-on-chip (EFIKA board). The environment is very > > > > > >>>> simplistic: RAM disk based root fs, as > > > > > >>>> there's no peripherals drivers besides serial console and the > > > > > >>>> built- in > > > > > >>>> PIC. See this log: > > > > > >>>> http://people.freebsd.org/~raj/logs/efika.log > > > > > >>> > > > > > >>> Wow, great news! Two questions: > > > > > >>> - are there any plans to support additional devices? > > > > > >> > > > > > >> We don't have immediate plans for other devices drivers, but > > > > > >> this basic support will be merged into SVN, and it would be > > > > > >> greatly welcome to see people help with remaining items. > > > > > > > > > > > > Is there a patch available? I would like to get back to working > > > > > > on the EFIKA. > > > > > > > > > > Preliminary diff against 2009.04.06 HEAD is here: > > > > > http://people.freebsd.org/~raj/patches/powerpc/efika.diff > > > > > > > > > > Comments or questions welcome. Some bits need to be streamlined so > > > > > that all AIM/OF variations work together, and the code has to be > > > > > rebased against up-to-date HEAD. > > > > > > > > I have downloaded your diff and succesfully patched it to -HEAD > > > > (checked out on 2009-08-25). > > > > Right now I'm looking into getting the USB controller working. (That > > > > would allow me to use network & disks all in one go.) > > > > > > > > I have written the OHCI attachment code (inspired by a mix of > > > > Warner's atmel version, mpc5xxx/ic.c and uart_dev_psc.c) and gotten > > > > it to succesfully attach to the OHCI controller when booting the > > > > Efika board. USB is not (yet) working correctly. Near the end of > > > > ohci_init(), the board seems to halt completely for about 30 seconds > > > > and after that, the OHCI controller sets the 'unrecoverable error' > > > > flag. > > > > > > > > A complete dmesg dump can be found here : > > > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28-ohci_attaching_bu > > > >t_ fa il ing.txt The kernel that produced this can be downloaded here > > > > : > > > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28-ohci_attaching_bu > > > >t_ fa il ing.kernel > > > > > > > > The files I added/changed to get the attachment of the OHCI > > > > controller to 'work' can be found here : > > > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28_changed_files.tar > > > >.g z (Warning : Ugly! and full of printf's for now!) > > > > (I could have missed one, let me know if you can't get it to work.) > > > > > > > > The above dmesg shows a number of printf's I've added to ohci.c . My > > > > mutilated version can be found here : > > > > http://vehosting.nl/pub_diffs/efika-daan-2009-08-28_ohci.c > > > > > > > > As you can see, I printf() the interrupt status register at various > > > > points during ohci_init(). The 'unrecoverable error' flag gets set > > > > just a couple of miliseconds after the following command has been > > > > executed : > > > > > > > > /* And finally start it! */ > > > > OWRITE4(sc, OHCI_CONTROL, ctl); > > > > > > > > After that OWRITE4(), the board sits for about 30 seconds and then > > > > continues. I'm just guessing what's going on here, but could it be > > > > that (one of?) the endpoint lists isn't properly setup and that the > > > > OHCI controller keeps the CPU from accessing memory while it's racing > > > > through memory following corrupt/invalid 'next' pointers? > > > > > > Maybe busdma is not computing correct physical addresses for the kernel > > > virtual memory loaded into DMA. > > > > I've looking closely at the logs I generated earlier and this doesn't > > seem to be the case (I think). The physical address of the HCCA (Host > > Controller Communications Area) looks the same and the frame_number > > counter is advancing in this memory area as soon as the controller is > > enabled. One thing that strikes me is the value of the frame number > > though : > > > > ohci_dumpregs:599: ohci_dumpregs: rev=0x00000010 control=0x00000093 > > command=0x00000002 > > ohci_dumpregs:603: intrstat=0x00000040 intre=0x8000005a intrd=0x8000005a > > ohci_dumpregs:607: hcca=0x01c12a00 percur=0x48000060 ctrlhd=0x01c20880 > > ohci_dumpregs:611: ctrlcur=0x00000000 bulkhd=0x01c20800 > > bulkcur=0x00000000 ohci_dumpregs:615: done=0x00000000 fmival=0xa7782edf > > fmrem=0x800025e7 ohci_dumpregs:619: fmnum=0x000000e5 perst=0x00002a2f > > lsthrs=0x00000628 ohci_dumpregs:623: desca=0x02001202 descb=0x00000000 > > stat=0x00000000 ohci_dumpregs:626: port1=0x00100303 port2=0x00010101 > > ohci_dumpregs:632: HCCA: frame_number=0x35fe0000 done_head=0x00000000 > > > > The frame number at this particular moment is '0x35fe0000', though the > > OHCI spec says it should be a 16 bit counter, followed by 16 bits of > > padding (that should read back as '0'). > > > > Could it be a big-endian controller, while the USB code expects > > little-endian? > > Yes, that was it. Changing every 'htole32' into 'htobe32' and every > 'le32toh' into 'be32toh' in sys/dev/usb/controller/ohci.c gets the USB > controller to work : Looking at the NetBSD USB code, I see they have tackled this same problem some time ago by adding a member to struct ohci_softc called 'sc_endian'. Byte swapping is done depending on it's value (which is set in attach routines where needed). Based on NetBSD's code, I've put together a diff against our current ohci.[ch] that adds the same functionality. With this change, I can get the OHCI controller on the Efika board to work, without breaking other controllers. The diff can be found here : http://vehosting.nl/pub_diffs/ohci-patch-endianness-2009-08-30.diff Could you consider adding it? -- Daan Vreeken VEHosting http://VEHosting.nl tel: +31-(0)40-7113050 / +31-(0)6-46210825 KvK nr: 17174380 From bugmaster at FreeBSD.org Mon Aug 31 11:07:13 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 31 11:09:13 2009 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200908311107.n7VB7CKc070669@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 power/135576 ppc gdb cannot debug threaded programs on ppc o power/133503 ppc [sound] Sound stutter after switching ttys o power/133383 ppc firefox thr_kill crash with heavy vm load o power/133382 ppc [install] Installer gets signal 11 o power/131548 ppc ofw_syscons no longer supports 32-bit framebuffer a power/121407 ppc [panic] Won't boot up; strange error message. o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 8 problems total.