Following are the FDC List......
1. 37c78
2. 82077AA
3. 82087
4. 279x
5. DP8473
6. W83977F
7. PD765A etc.....
Now My question is, If u have developed FDC for all, then How to know which FDC ur system is using. So that u can develope a portable face for Floppy Device............
Handling different floppy controllers..
Handling different floppy controllers..
Last edited by Mohanty on Sat Oct 02, 2010 1:51 am, edited 1 time in total.
- thepowersgang
- Member
- Posts: 734
- Joined: Tue Dec 25, 2007 6:03 am
- Libera.chat IRC: thePowersGang
- Location: Perth, Western Australia
- Contact:
Re: Questions About Floppy???????
The typical way of handling the FDC is to assume a 82077AA or similar and use the IO range 0x3F0-0x3F7
If the device doesn't present itself there, then just write another driver that detetects that chip and reads/writes it.
P.S. Could you please reduce the number of question marks in your topics?, and it's nice if the topic titles are more descriptive, e.g. this topic could have been "Handling different floppy controllers"
If the device doesn't present itself there, then just write another driver that detetects that chip and reads/writes it.
P.S. Could you please reduce the number of question marks in your topics?, and it's nice if the topic titles are more descriptive, e.g. this topic could have been "Handling different floppy controllers"
Kernel Development, It's the brain surgery of programming.
Acess2 OS (c) | Tifflin OS (rust) | mrustc - Rust compiler
Currently Working on: mrustc
Acess2 OS (c) | Tifflin OS (rust) | mrustc - Rust compiler
Currently Working on: mrustc
Re: Questions About Floppy???????
hahahah....., Thank u so much, For ur suggestion....and thank u so much for suggesting the title. That is completely appropriate..........thepowersgang wrote: P.S. Could you please reduce the number of question marks in your topics?, and it's nice if the topic titles are more descriptive, e.g. this topic could have been "Handling different floppy controllers"
I will change that...
Then what's about the other FDC, How can I Identify Them..thepowersgang wrote: The typical way of handling the FDC is to assume a 82077AA or similar and use the IO range 0x3F0-0x3F7
Re: Handling different floppy controllers..
I'd just like to congratulate the mod who changed the ridiculous title of this topic. I came here to do the exact same thing.
SatyaNarayan, there is no need to put seven question marks in a topic title. Also, we know it contains a question because you're posting in the "OS Development" section of the forum.
So please title your posts something informative and somewhat less irritating, like the newly retitled "handling different floppy controllers".
Thanks,
James
SatyaNarayan, there is no need to put seven question marks in a topic title. Also, we know it contains a question because you're posting in the "OS Development" section of the forum.
So please title your posts something informative and somewhat less irritating, like the newly retitled "handling different floppy controllers".
Thanks,
James
- thepowersgang
- Member
- Posts: 734
- Joined: Tue Dec 25, 2007 6:03 am
- Libera.chat IRC: thePowersGang
- Location: Perth, Western Australia
- Contact:
Re: Handling different floppy controllers..
[quote=SatyaNarayan]
Then what's about the other FDC, How can I identify them?
[/quote]
I am unsure about the other chips personally, but I would assume that if they don't behave the same as (or at least, similarly to) the 82077AA then their datasheets would tell you how to detect and program them.
In 99% of cases however, the controllers you will come across will be compatible with the 82077AA (if you look at Floppy_Disk_Controller, it says that that chip is not acutally used anymore, but is instead emulated by the chipset), so you only need to write a single driver.
Then what's about the other FDC, How can I identify them?
[/quote]
I am unsure about the other chips personally, but I would assume that if they don't behave the same as (or at least, similarly to) the 82077AA then their datasheets would tell you how to detect and program them.
In 99% of cases however, the controllers you will come across will be compatible with the 82077AA (if you look at Floppy_Disk_Controller, it says that that chip is not acutally used anymore, but is instead emulated by the chipset), so you only need to write a single driver.
Kernel Development, It's the brain surgery of programming.
Acess2 OS (c) | Tifflin OS (rust) | mrustc - Rust compiler
Currently Working on: mrustc
Acess2 OS (c) | Tifflin OS (rust) | mrustc - Rust compiler
Currently Working on: mrustc