At 05:27 PM 5/30/2006, Bao C. Ha wrote:
I think it is a kernel issue. On Via-based hardware, the CF socket
cannot handle DMA, just PIO, not until the c7-based systemboard
arriving later this year. These high capacity and fast CF will
keep choking on these boards during boot-up.
The WRAP CF card supports (apparently) DMA33, so it's not quite that
simple. From my boot sequence:
atapci0: <National Geode SC1100 ATA33 controller> port
0x1f0-0x1f7,0x3f6,0x170-0
x177,0x376,0xfc00-0xfc0f at device 18.2 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
The CF device is on ata0-master.
BUT, as I just found out, reading the WRAP docs:
"Another possible issue are cards with IDE DMA support the DMA signals
are a fairly recent
addition to the CF spec, and are not supported by WRAP. If you experience
problems with IDE
access later in the boot process, try to disable IDE DMA in your operating
system."
To test this theory, is there a way to tell the boot sequence to use only
PIO for disk access, or do we need to build a new kernel?
I'm completely bummed out by this discovery, which was just sitting there
waiting for discovery. Yes, if I can get the embedded platform to run on my
Seagate ST1.2 by using PIO, I'll do it, but there goes some of the benefit
of the real hard disk.
Bill Plein
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
