No subject
Mon Jun 25 13:53:28 EDT 2007
Block devices:
1 ramdisk
3 ide0
31 mtdblock
>Thanks again,
>Don
>
>-----Original Message-----
>From: "Tommy B" [mailto:gentoo at nc.rr.com]
>Sent: Tuesday, October 11, 2005 12:44 PM
>To: Avila
>Subject: Re: [Avila] CF block driver ?
>
>
>Don Osburn wrote:
>
>
>
>>First,
>>thanks to everyone on this list for all the past help. This is a great
>>community.
>>
>>
>>
>>
>Communities do rock, good ones anyway :)
>
>
>
>>Second,
>>is there a block driver for CF available here, or anywhere? I need to
>>support reading / writing FAT files onto the CF so I can move data back and
>>forth between the windoze world, and the embedded IXP. What I want to do
>>
>>
>is
>
>
>>use the native msdos and fat modules, and just mount the CF. However, this
>>requires a block driver for the CF/IDE interface. I have the char driver,
>>and I can emulate the FAT "stuff" in my application, (I can manage reading
>>and writing to the sectors, etc), but I would REALLY like to just use the
>>native FAT modules. Is that available somewhere?
>>
>>
>>
>>
>>
>The Avila CF/IDE driver is GPL'd so that's probably available. There's
>also the Intel app note, but that is most likely overkill. Rebuilding
>the kernel with FAT support is straight forward. If you are setup for
>rebuilding kernels.
>
>For sharing with a PC just run samba. The device then just looks like a
>Windows box on the network or scp (secure copy) which is part of the SSH
>suite.
>
>
>
>>Finally, what is the issue with hot swapping on the CF? Why can I hot plug
>>CF cards into PCs and everything else, but I can't do it to an embedded
>>IXP4xx device? We've been trying to run that one down, but haven't figured
>>it out yet.
>>
>>
>>
>>
>>
>I'm no HW engineer, but here's my understanding of the situation. The CF
>interface hangs off the Expansion bus which is directly connected to the
>processor. This makes for low-cost "glueless" connections. It also
>means no electrical isolation. You're trading cost and size for losing
>hotplug.
>A CPLD or FPGA could electrically isolate the CF/IDE interface but it
>adds size and cost to the board. Size in both the physical layout, and
>cost for the layout, chips and NRE to do the design and programming of
>the devices. It's simply a design cost tradeoff and there's probably
>not much of a market for it.
>
>Cheers,
>
>Tom
>
>
>
>>Thanks again.
>>Regards,
>>Don
>>
>>
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
>For additional commands, e-mail: avila-help at lists.unixstudios.net
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
>For additional commands, e-mail: avila-help at lists.unixstudios.net
>
>
>
>
More information about the Avila
mailing list