Re: Customizing ubldr build...
On May 24, 2012, at 6:35 AM, Tim Kientzle wrote: I think the PandaBoard ES is fully supported by U-Boot, so it should be possible to use ubldr as part of the boot chain for that just like I've been doing with BeagleBone. What are the benefits of using ubldr compared to what we are doing today(load; go)? Damjan___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Customizing ubldr build...
On May 24, 2012, at 10:25 AM, Aleksandr Rybalko wrote: On Thu, 24 May 2012 10:16:42 +0200 Damjan Marion dmar...@freebsd.org wrote: On May 24, 2012, at 6:35 AM, Tim Kientzle wrote: I think the PandaBoard ES is fully supported by U-Boot, so it should be possible to use ubldr as part of the boot chain for that just like I've been doing with BeagleBone. What are the benefits of using ubldr compared to what we are doing today(load; go)? Preload modules for example. (if it accessible of course) I was looking into this few months ago but I didn't found a value in doing this in embedded world where we already have custom kernel for each SoC/board. Maybe we will have GENERIC arm kernel one day, but there is long road Damjan___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Customizing ubldr build...
On May 24, 2012, at 12:03 PM, Aleksandr Rybalko wrote: both with FreeScale i.MX515 ARM SoC + 4M NOR for loader (I put second uboot + ubldr into it) + 8G SSD Didn't know that we have support for i.MX515. Is it in svn? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Customizing ubldr build...
On May 24, 2012, at 4:30 PM, Warner Losh wrote: On May 24, 2012, at 3:40 AM, Damjan Marion wrote: On May 24, 2012, at 10:25 AM, Aleksandr Rybalko wrote: I was looking into this few months ago but I didn't found a value in doing this in embedded world where we already have custom kernel for each SoC/board. Maybe we will have GENERIC arm kernel one day, but there is long road I'm working on that, at least for all Atmel kernels. We'll have at least three kernels though: armv4 little endian, armv4 big endian and armv6 little endian. Even for atmel, some of the id registers are such we may need multiple kernels. I guess they all use same interrupt controller. Currently there can be only support for one intc built in kernel so that needs serious rework. Damjan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Status of clang/llvm cross-compiling for ARM
Hi, Just to briefly share with wider audience progress on cross-compiling for ARM using llvm/clang. I managed to cross-compile kernel with clang for Marvel SoC and run world compiled with gcc in multiuser. It works stable and I didn't notice any issues so far. Cross compiling even works from MacOS. Caveat is that it still requires binutils as integrated assembler is not stable enough. The real benefit of having clang in place is support of new ARM architectures (ARMv6, ARMv7) which are not supported in last GPLv2 gcc/binutils. With regards to building world, main issue is ARM ABI. FreeBSD uses ATPCS[1] procedure call standard which is older one. New one is called AAPCS [2] and introduces some important performance related stuff. llvm/clang doesn't support older ATPCS standard so it fails to build some libraries. Andrew already did some work on moving to AAPCS[3]. When we will have AAPCS implemented then I expect that building of world should work without any major issues. Damjan [1] http://infocenter.arm.com/help/topic/com.arm.doc.espc0002/ATPCS.pdf [2] http://infocenter.arm.com/help/topic/com.arm.doc.ihi0042d/IHI0042D_aapcs.pdf [3] http://svnweb.freebsd.org/base/projects/arm_eabi/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: atkbdc broken on current ?
On Jun 20, 2011, at 2:51 PM, John Baldwin wrote: On Sunday, June 19, 2011 7:05:04 pm Damjan Marion wrote: On Jun 17, 2011, at 11:21 PM, John Baldwin wrote: On Friday, May 06, 2011 11:47:33 am John Baldwin wrote: On Thursday, May 05, 2011 5:04:54 pm Damjan Marion wrote: On May 5, 2011, at 7:43 PM, John Baldwin wrote: On Thursday, May 05, 2011 9:21:04 am Damjan Marion wrote: Hi, I have issue with old HP DL380G3 server. When I use ILO virtual console to manage server. Seems that 9-CURRENT fails to detect atkbdc. When I boot 8.2-RELEASE it works well. 8.2 dmesg shows: atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 9.0: atkbdc0: Keyboard controller (i8042) failed to probe at port 0x60 on isa0 Is this a known issue? Should I enable some additional outputs, like KBDIO_DEBUG? I suspect this is a resource issue stemming from changes I made to the acpi(4) bus driver quite a while ago to make it use rman_reserve_resource(). Can you capture a full verbose dmesg from 9 along with devinfo -rv and devinfo -ur output from 9? Here it is: http://web.me.com/dmarion/atkbdc.txt Ohh, hmm. Your BIOS has done odd things: isab0 pnpinfo vendor=0x1166 device=0x0201 subvendor=0x1166 subdevice=0x0201 class=0x060100 at slot=15 function=0 handle=\_SB_.PCI0.IBRG isa0 I/O ports: 0x0-0xf 0x20-0x21 0x40-0x43 0x60 0x61 0x64 0x80-0x8f 0xa0-0xa1 0xc0-0xdf 0x4d6 Still, I don't know how the ISA bus is actually allocating resources. Can you add some code to the x86 nexus driver to drop into kdb when it receives a SYS_RES_IOPORT allocation request from isa0 and get a stack trace from DDB and reply with the trace? So I think I just found the explanation for this and I think the change I just committed will fix your system: Author: jhb Date: Fri Jun 17 21:19:01 2011 New Revision: 223207 URL: http://svn.freebsd.org/changeset/base/223207 Hi John, sorry for not coming back to you on your previous email, it was on my todo list but I haven't time to do it. I tried now new kernel and it works well. Thanks for fixing this. Thanks. Can you capture an acpdump from your box when you get a chance and send it to me? I want to make sure if I make any other changes in this area that your box will still work. Sure, I will unicast it to you. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: best way to do FreeBSD kernel/userland development on OSX ?
On Jun 20, 2011, at 10:53 PM, Luigi Rizzo wrote: i recently replaced my laptop with a mac, which opens the problem on how do i do FreeBSD development (including kernel work) on it. the option i am trying now is running a freebsd VM in virtualbox, but it is slightly slow and probably energy hungry. I'd like to keep the svn checkut outside the disk image but unfortunately the default filesystem on osx is case-insensitive so i can't do that -- unless someone shows me how to change the filesystem conventions. According to some email threads this is not a smart option as it might screw up some applications which assume that FS is case-insensitive. I shrink my 1st partition and created 2nd one which is case sensitive. i'm using it for cross-compiling FreeBSD/ARM kernel. Damjan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: atkbdc broken on current ?
On Jun 17, 2011, at 11:21 PM, John Baldwin wrote: On Friday, May 06, 2011 11:47:33 am John Baldwin wrote: On Thursday, May 05, 2011 5:04:54 pm Damjan Marion wrote: On May 5, 2011, at 7:43 PM, John Baldwin wrote: On Thursday, May 05, 2011 9:21:04 am Damjan Marion wrote: Hi, I have issue with old HP DL380G3 server. When I use ILO virtual console to manage server. Seems that 9-CURRENT fails to detect atkbdc. When I boot 8.2-RELEASE it works well. 8.2 dmesg shows: atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 9.0: atkbdc0: Keyboard controller (i8042) failed to probe at port 0x60 on isa0 Is this a known issue? Should I enable some additional outputs, like KBDIO_DEBUG? I suspect this is a resource issue stemming from changes I made to the acpi(4) bus driver quite a while ago to make it use rman_reserve_resource(). Can you capture a full verbose dmesg from 9 along with devinfo -rv and devinfo -ur output from 9? Here it is: http://web.me.com/dmarion/atkbdc.txt Ohh, hmm. Your BIOS has done odd things: isab0 pnpinfo vendor=0x1166 device=0x0201 subvendor=0x1166 subdevice=0x0201 class=0x060100 at slot=15 function=0 handle=\_SB_.PCI0.IBRG isa0 I/O ports: 0x0-0xf 0x20-0x21 0x40-0x43 0x60 0x61 0x64 0x80-0x8f 0xa0-0xa1 0xc0-0xdf 0x4d6 Still, I don't know how the ISA bus is actually allocating resources. Can you add some code to the x86 nexus driver to drop into kdb when it receives a SYS_RES_IOPORT allocation request from isa0 and get a stack trace from DDB and reply with the trace? So I think I just found the explanation for this and I think the change I just committed will fix your system: Author: jhb Date: Fri Jun 17 21:19:01 2011 New Revision: 223207 URL: http://svn.freebsd.org/changeset/base/223207 Hi John, sorry for not coming back to you on your previous email, it was on my todo list but I haven't time to do it. I tried now new kernel and it works well. Thanks for fixing this. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
atkbdc broken on current ?
Hi, I have issue with old HP DL380G3 server. When I use ILO virtual console to manage server. Seems that 9-CURRENT fails to detect atkbdc. When I boot 8.2-RELEASE it works well. 8.2 dmesg shows: atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 9.0: atkbdc0: Keyboard controller (i8042) failed to probe at port 0x60 on isa0 Is this a known issue? Should I enable some additional outputs, like KBDIO_DEBUG? Thanks, Damjan___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: atkbdc broken on current ?
On May 5, 2011, at 7:43 PM, John Baldwin wrote: On Thursday, May 05, 2011 9:21:04 am Damjan Marion wrote: Hi, I have issue with old HP DL380G3 server. When I use ILO virtual console to manage server. Seems that 9-CURRENT fails to detect atkbdc. When I boot 8.2-RELEASE it works well. 8.2 dmesg shows: atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 9.0: atkbdc0: Keyboard controller (i8042) failed to probe at port 0x60 on isa0 Is this a known issue? Should I enable some additional outputs, like KBDIO_DEBUG? I suspect this is a resource issue stemming from changes I made to the acpi(4) bus driver quite a while ago to make it use rman_reserve_resource(). Can you capture a full verbose dmesg from 9 along with devinfo -rv and devinfo -ur output from 9? Here it is: http://web.me.com/dmarion/atkbdc.txt Thanks, Damjan___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
