Date: Tue, 6 May 2003 02:04:25 +0300
From: Halil Demirezen <nitrium@bilmuh.ege.edu.tr>
To: Thomas Horsten <thomas@horsten.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: about bios
Message-ID: <20030505230425.GA17060@bilmuh.ege.edu.tr>
References: <20030505225013.GA5375@bilmuh.ege.edu.tr> <Pine.LNX.4.40.0305060041550.7106-100000@jehova.dsm.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.40.0305060041550.7106-100000@jehova.dsm.dk>
User-Agent: Mutt/1.3.28i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1110
Lines: 31

> 
> What you do in the BIOS does not only disable the BIOS calls for the
> floppy controller, it turns it completely off in the chipset (software
> disconnect) so it is never accessed with the IO access, and therefore is
> not detected.
> 
> It would probably be possible to turn it on again in floppy.c, but it
> would be chipset dependent how to do it.
> 
> Cheers,
> Thomas
> 


So can we say that, during initialization, setup.s pushes some bios info 
to the memory, and then after entering protected mode in i386, it pops
these information and sets kernel depending on it. Because of absence of
FDC controller info at this data area linux does not recognize FDC. However,

I can turn it on still usin IO ports and using in, out assembly instructions.

what i mention above for sure is not correct, however, is the procedure something like that?

thank you..

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/