From: tim <twojtasz@puma.dpg.devry.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan9.ini options for ide i/o port settings?
Date: Wed, 12 Dec 2001 09:48:28 +0000 [thread overview]
Message-ID: <7e90b10a.0112111309.2fe4c20@posting.google.com> (raw)
In-Reply-To: <20011211163820.93255199B5@mail.cse.psu.edu>
If thats the case I should be able to hook it up to the normal ata
interface, to at least install, then I can fix that driver :) Thanks.
jmk@plan9.bell-labs.com wrote in message news:<20011211163820.93255199B5@mail.cse.psu.edu>...
> There's currently no way to do that. The device has to be recognised
> from the PCI vendor and device ID in the driver.
>
> The driver code is deliberately conservative, there are many broken
> devices out there. However, it would not be much of a stretch to allow
> any unrecognised controller to be used in non-DMA mode.
next prev parent reply other threads:[~2001-12-12 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 16:38 jmk
2001-12-12 9:48 ` tim [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-11 10:07 tim
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=7e90b10a.0112111309.2fe4c20@posting.google.com \
--to=twojtasz@puma.dpg.devry.edu \
--cc=9fans@cse.psu.edu \
/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).