From: ebiederman@lnxi.com (Eric W. Biederman)
To: "ganesh_borse" <ganesh_borse@indiatimes.com>
Cc: <ebiederman@lnxi.com>, <agnew@missl.cs.umd.edu>,
<linux-kernel@vger.kernel.org>
Subject: Re: Request for help
Date: 02 Jun 2003 11:49:01 -0600 [thread overview]
Message-ID: <m3fzmsjroy.fsf@maxwell.lnxi.com> (raw)
In-Reply-To: <200305290413.JAA23492@WS0005.indiatimes.com>
I am CC'ing linux-kernel as that is the general kernel list. There
may be something even more focused on IDE issues but I am
not aware of it.
"ganesh_borse" <ganesh_borse@indiatimes.com> writes:
> Hi,
>
>
> I would like to request for a little help related to IDE controllers.
>
>
> I am trying to develop a device drive code for listing the devices connected to
> a ide controller at the time of kernel booting.
>
>
>
> Is there any way to get which channels on ide controller has got devices and
> which devices?
Yes. But it is baroque.
> This I am trying to get even before the normal ide device driver
> has been setup. Are there ide controller commands to get this info?
Not exactly. The method is essentially you ping the drives to see
if they are there.
> Or is this
> info stored in registers of ide-controllers?
Nope this information is not stored in registers.
> For this do we need to write
> assembly instructions on linux?
No.
But there is also nothing that allows you to force the module
order within the kernel. So there are no guarantees you will
come before a normal IDE driver. I assume from the questions
you intend to have this working in the linux kernel.
Eric
next parent reply other threads:[~2003-06-02 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200305290413.JAA23492@WS0005.indiatimes.com>
2003-06-02 17:49 ` Eric W. Biederman [this message]
2003-06-02 18:48 ` Request for help Andy Pfiffer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3fzmsjroy.fsf@maxwell.lnxi.com \
--to=ebiederman@lnxi.com \
--cc=agnew@missl.cs.umd.edu \
--cc=ganesh_borse@indiatimes.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).