From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] i82365 change
Date: Tue, 28 May 2002 15:27:22 +0100 [thread overview]
Message-ID: <a42c4c41515707727c63f090d4c5cf7e@9fs.org> (raw)
That bit only exists in 82365SL-DF compatible versions of the chip.
Are we sure that this won't break other vendors chips, or stop 5V
devices working?
next reply other threads:[~2002-05-28 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 14:27 nigel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-28 15:00 Fco.J.Ballesteros
2002-05-28 14:47 nigel
2002-05-28 14:33 Fco.J.Ballesteros
2002-05-28 14:04 Fco.J.Ballesteros
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=a42c4c41515707727c63f090d4c5cf7e@9fs.org \
--to=nigel@9fs.org \
--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).