Our target system is based on a PIII CPCI board with Intel 82801BA IDE
controller. It boots off a CF card connected as a master device on channel
0.
We had no problem with this configuration until we received new batch of
CF cards. The difference between old and new ones is in DMA support. CF
vendors start adding Multiword DMA support in accordance to the 2.1 CF
Specification. The new CF supports 0,1, and 2 MDMA modes. Active mode is 2.
In new configuration, when devb-eide starts it instantly finds IDE device
and then it takes 2 minutes before hd0 appears in /dev directory. After
boot everythig works fine. The only solution to avoid this 2 minute delay
I found is “chnl=0,master=mdma=off”. The “mdma=2” does not help.
Is there anything I can do to eliminate this delay and enable mdma?
Currently we’re using 6.2.1B. Maybe it is fixed in 6.3?
Sincerely,
Serge
By the way, for the CompactFlash cards with MDMA the “blk automount=hd0:/”
does not work. I have to add mount utility to the boot image, wait till
/dev/hd0 appears, and then explicitly call “mount /dev/hd0 /”.
Our target system is based on a PIII CPCI board with Intel 82801BA IDE
controller. It boots off a CF card connected as a master device on channel
0.
We had no problem with this configuration until we received new batch of
CF cards. The difference between old and new ones is in DMA support. CF
vendors start adding Multiword DMA support in accordance to the 2.1 CF
Specification. The new CF supports 0,1, and 2 MDMA modes. Active mode is 2.
In new configuration, when devb-eide starts it instantly finds IDE device
and then it takes 2 minutes before hd0 appears in /dev directory. After
boot everythig works fine. The only solution to avoid this 2 minute delay
I found is “chnl=0,master=mdma=off”. The “mdma=2” does not help.
Is there anything I can do to eliminate this delay and enable mdma?
Currently we’re using 6.2.1B. Maybe it is fixed in 6.3?
Sincerely,
Serge