On Feb 7, 2008 11:16 AM, Marc Jones <[EMAIL PROTECTED]> wrote:
> I preferred the v2 way of doing this. If the AMD IDE device was found it
> got initialized. I think it needs a DTS and I think other southbridges
> with multiple PCI headers will need this too.
So it's more like the northbridge part
ron minnich wrote:
> This code now lets filo find IDE.
>
> but it locks up :-(
>
> oh well. attached.
>
> ron
>
I preferred the v2 way of doing this. If the AMD IDE device was found it
got initialized. I think it needs a DTS and I think other southbridges
with multiple PCI headers will need th
Commited rev 575
--
coreboot mailing list
coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
On Feb 6, 2008 10:21 PM, Corey Osgood <[EMAIL PROTECTED]> wrote:
> not __FUNCTION__ any more? I'm not sure what the current standards are,
__FUNCTION__ is gcc and acts kind of like a macro. __func__ is c99 and
acts like it is a const variable. You can start looking around at
postings about why _
On Thu, Feb 07, 2008 at 01:21:15AM -0500, Corey Osgood wrote:
> >+printk(BIOS_DEBUG, "cs5536_ide: %s\n", __func__);
>
> not __FUNCTION__ any more? I'm not sure what the current standards
> are,
__func__ is good.
http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Function-Names.html
//Peter
--
c
On Feb 7, 2008 1:15 AM, ron minnich <[EMAIL PROTECTED]> wrote:
> This code now lets filo find IDE.
>
> but it locks up :-(
>
> oh well. attached.
>
> ron
>
>+printk(BIOS_DEBUG, "cs5536_ide: %s\n", __func__);
not __FUNCTION__ any more? I'm not sure what the current standards are, but
either w
This code now lets filo find IDE.
but it locks up :-(
oh well. attached.
ron
With this set of changes FILO now reliably finds the IDE controller.
Press for default boot, or for boot prompt...
boot: hda1:/vmlinuz root=/dev/hda1 console=tty0 console=ttyS0,115200
malloc_diag: alloc: 240 bytes
7 matches
Mail list logo
