From: "James Buchanan" <jamesbuch@iprimus.com.au>
To: "Jeff Garzik" <jgarzik@pobox.com>
Cc: <linux-kernel@vger.kernel.org>, <alan@lxorguk.ukuu.org.uk>
Subject: Re: Anyone supporting Intel 8XX chipset???
Date: Mon, 3 Feb 2003 02:52:03 +1100 [thread overview]
Message-ID: <001d01c2cad3$079f8440$59951ad3@windows> (raw)
In-Reply-To: <3E3D3C55.2090805@pobox.com>
Hmm, thanks. Someone has pointed this out. I have asked Alan something and
I
just misinterpreted what he said.
Cheers -
J
----- Original Message -----
From: "Jeff Garzik" <jgarzik@pobox.com>
To: "James Buchanan" <jamesbuch@iprimus.com.au>
Cc: <linux-kernel@vger.kernel.org>; <alan@lxorguk.ukuu.org.uk>
Sent: Monday, February 03, 2003 2:42 AM
Subject: Re: Anyone supporting Intel 8XX chipset???
> > Is anyone writing code to directly support features of the Intel 800
series
> > chipsets? I'm using the 8xx chipset docs from Intel to gradually
> > implement (hopefully) all the features of the 800 series of chipsets.
>
> [...]
> > One thing: should I maintain the consistency of using /dev files?
Because there
> > is a hardware random number generator in the 800 series chipsets, and I
> > am wondering whether I should export this feature as a set of functions
or
> > a /dev file. (Both??)
>
>
> Methinks you need to find out what support already exists.
>
> The hardware RNG driver has existed for years, as has 3D support and ATA
> support...
>
> Jeff
>
>
>
>
> -
> 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/
prev parent reply other threads:[~2003-02-02 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-02 13:19 James Buchanan
[not found] ` <Pine.LNX.4.44.0302020939560.6653-100000@coffee.psychology. mcmaster.ca>
2003-02-02 14:49 ` James Buchanan
2003-02-02 15:42 ` Jeff Garzik
2003-02-02 15:52 ` James Buchanan [this message]
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='001d01c2cad3$079f8440$59951ad3@windows' \
--to=jamesbuch@iprimus.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.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
Powered by JetHome