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?
3 G$ o- h4 w' U) |* Z
有人能夠清楚的詳列在LINUX下porting IDE driver的步驟嗎?

olduncle

除了看書之外,最實際的方法就是參考别家的Source code
Linux的源碼就有很可供參考,不管是legacy IDE或是掛在SCSI下的libata
5 E. x( `  X- ~1 i9 B3 ~看個2~3隻driver,你就會清楚ATA的interface需要哪些structure及private function point.
0 C% ^$ v* u4 w' d8 I3 `; S而且Lnux本身就支援許多Filesystem,除非你是要hack filesystem,否則只要porting driver就夠了。

olduncle

除了看書之外,最實際的方法就是參考别家的Source code
Linux的源碼就有很可供參考,不管是legacy IDE或是掛在SCSI下的libata
7 }3 P6 d" I: H, G  c. O. [看個2~3隻driver,你就會清楚ATA的interface需要哪些structure及private function point.
2 r) i) y2 i0 \$ G4 i; D而且Lnux本身就支援許多Filesystem,除非你是要hack filesystem,否則只要porting driver就夠了。

jacky002

因為你是用uCLinux，所以我首先會問你有沒有將MMU的設定關掉，在我記憶中uCLinux是不支援MMU的。
4 h2 C1 r9 a/ v4 O- |: |
5 E( o8 a. B5 w/ \# Y其次，你是用ATAPI或是SCSI的driver layer去寫這個driver的。建議Driver path最好還是使用SCSI會比較好，其實底層都類似，只不過SCSI再上層多做了一層，轉了一層SCSI command，也補強之前ATAPI的部分不足。
5 Q9 Q- m' k4 R0 {  R) w
9 D" Q1 ~  W7 h6 p4 v給你參考，希望對你有所幫助。

windflowerz

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

tommywgt

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

tommywgt

好巧...這本書我有也...
+ |' C$ b: G" M" R
不過還是謝了
' U# t# _2 q  q# {. b% s. V7 ^
大大願意在這跟大家分享的話論壇的後進都會感謝你的...

kevin

我想你的問題是如何寫 Uclinux ide/ATA 的 driver.
可以參考O'Reilly "Linux Device Drivers" book.
7 T4 `& x) ]& C% \code example 在 http://examples.oreilly.com/linuxdrive3/

tommywgt

另外這有二個很重要的網站
7 R5 s% ^- R) w/ [& S3 Pwww.t10.org SCSI
' T2 i  r' X4 d# a9 |- Gwww.t13.org ATAPI

2 ^; N: k+ B/ v4 v+ {& C我在design HD controller時就是根據這二個網站資料的

tommywgt

這一段是說明如何用ata driver改成sata, 照道理來講就是改drivers/ide這一段的code就對了.
' q  ^/ i" `9 ]) G$ Q6 J有人能再補充更多的嗎?

Driver Overview: Linux kernels have two ATA ("IDE") driver sets:
, _1 M8 d) q3 G" C2 R# W5 P
"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.

Optionally, 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):

7 |4 Q# O& X/ J3 V. @5 }! v& JFor 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.
- }+ n9 d* ], H9 X9 F' ?- L
For 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.
1 h6 O& a- v% N! y1 C# O' m" h: l
"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.

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.