proting IDE driver for uclinux/linux

tommywgt

我在Xilinx FPGA(EDK8.2)引用了MicroBlaze 32 bits RISC CPU, 可以RUN uclinux, 現在我又設計了一個非標準的IDE, 我自己寫個程式去R/W HD, 400G的也沒問題, 我也寫了一個FAT32 file system透過FAT32的LIB我所做的檔案操作, 使得HD接到WINDOWS也可以RUN的很正常. 但是問題來了, 這些自己寫的HD LIB無法跟uclinux KERNEL結合, 以致於無法直接跟系統資源結合, 也無法在VFS內mount這個device?
7 m  _6 M3 M7 k
! l! Q$ ]* W, X: c有人能夠清楚的詳列在LINUX下porting IDE driver的步驟嗎?

olduncle

除了看書之外,最實際的方法就是參考别家的Source code
Linux的源碼就有很可供參考,不管是legacy IDE或是掛在SCSI下的libata
- w% Z4 U" J6 Z. s' z5 e' C5 n看個2~3隻driver,你就會清楚ATA的interface需要哪些structure及private function point.
而且Lnux本身就支援許多Filesystem,除非你是要hack filesystem,否則只要porting driver就夠了。

olduncle

除了看書之外,最實際的方法就是參考别家的Source code
5 f8 \1 _0 T- \' j0 K9 GLinux的源碼就有很可供參考,不管是legacy IDE或是掛在SCSI下的libata
! Q9 Y5 O+ ^" b看個2~3隻driver,你就會清楚ATA的interface需要哪些structure及private function point.
而且Lnux本身就支援許多Filesystem,除非你是要hack filesystem,否則只要porting driver就夠了。

jacky002

因為你是用uCLinux，所以我首先會問你有沒有將MMU的設定關掉，在我記憶中uCLinux是不支援MMU的。
% {  K8 [5 g. }+ ~# }
* ?  G) j, C$ f- X) J3 Q其次，你是用ATAPI或是SCSI的driver layer去寫這個driver的。建議Driver path最好還是使用SCSI會比較好，其實底層都類似，只不過SCSI再上層多做了一層，轉了一層SCSI command，也補強之前ATAPI的部分不足。
% W8 N9 I  K& u, h9 ^2 O
; g5 f/ q! s7 ?0 c; p給你參考，希望對你有所幫助。

windflowerz

我隻能幫妳頂一下，非常抱歉，幫不暸忙哦

tommywgt

沒人回也...我自己推一下好了, 不然只好找時間自己回了...鳴

tommywgt

好巧...這本書我有也...
9 U0 h; y+ G% C% F7 s% V, y* F
不過還是謝了

& Y' N; |& E/ u% z大大願意在這跟大家分享的話論壇的後進都會感謝你的...

kevin

我想你的問題是如何寫 Uclinux ide/ATA 的 driver.
( w$ S6 l  g) A9 a. |" v) B可以參考O'Reilly "Linux Device Drivers" book.
code example 在 http://examples.oreilly.com/linuxdrive3/

tommywgt

另外這有二個很重要的網站
& g2 R) i0 G& ^/ s# N! g  nwww.t10.org SCSI
3 [% [+ T  e! _) y! }0 Hwww.t13.org ATAPI
6 D4 l+ I5 k; |& D+ }/ n9 {
我在design HD controller時就是根據這二個網站資料的

tommywgt

這一段是說明如何用ata driver改成sata, 照道理來講就是改drivers/ide這一段的code就對了.
有人能再補充更多的嗎?

Driver Overview: Linux kernels have two ATA ("IDE") driver sets:
5 H( v7 }3 I+ F( }
8 d" k% i" n& |"drivers/ide": This is the traditional ATA driver set, maintained by Bartlomiej Zolnierkiewicz (before that, Andre Hedrick). Contrary to popular belief, it includes low-level drivers for many common SATA chipsets.

' e! k9 D0 [1 l- s* e, XOptionally, on top of drivers/ide block-device (generic mass storage access) drivers, one can load drivers to provide software-level suport for BIOS services enabling various types of manufacturer-specific software RAID (called "fakeraid", below):

For 2.4 kernels, Linux's software-RAID (fakeraid) driver collection is called "ataraid", which has subdrivers for the various manufacturers' different software RAID schemes. Using ataraid results in your partitions being addressed using a /dev/ataraid/d0p1 (etc.) device-naming convention. Note: Support greatly improved circa-2.4.23.
. J- s' X8 g1 c5 P
3 L& F0 E8 D4 Y8 x0 FFor 2.6 kernels, Linux's software-RAID (fakeraid) driver collection is called "dmraid" (Device Mapper RAID). So far (Sept 2004), Promise Fasttrack, HighPoint 37X, Intel ICH5/6, LSI, and SiI 3112A/Medley are supported: http://tienstra4.flatnet.tudelft.nl/~gerte/gen2dmraid/

I'm pretty sure manufacturers' proprietary drivers, where available, are designed to fit the above framework.

"libata": This is the newer ATA driver set for selected SATA chipsets only, maintained by Jeff Garzik, leveraging the kernel's well-tested SCSI layer. Garzik developed it in the 2.6 kernel series. 2.4 support was available only with a backported patch until libata's inclusion in 2.4.27 and later.
1 b' l) v! C* f$ X. X
libata causes each SATA port appear as a new SCSI bus. There are individual low-level drivers for the individual SATA chipsets, e.g., ahci, ata_adma, ata_piix, sata_nv, sata_promise, sata_sil, sata_sx4, sata_svw, sata_via, sata_vsc.