mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Buchanan <jamesbuch@iprimus.com.au>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: Anyone supporting Intel 8XX chipset???
Date: Mon, 03 Feb 2003 00:19:08 +1100	[thread overview]
Message-ID: <5.1.0.14.0.20030203000618.00a0eb20@pop.iprimus.com.au> (raw)

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.

The support of the I/O hubs and so on to get rid of relying on legacy
PC/AT stuff will take a while.

I have a couple of questions because I'm new to kernel contributions.
I'll be working in two main files, i8xx.h and i8xx.c, possibly i8xx.s too.
In the early stages I may have a directory /i8xx and implementation of
specific features will go into there in separate files.

Now, I need to add an option like -DHAVE_INTEL800_CHIPSET to the kernel
configuration so my code can see if we should compile in this stuff.

Where does it go?  I will only make patches for the kernel files that deal with
that, and I will be patching against 2.4.20.  All my chipset stuff will 
otherwise
be in separate files.

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??)

Thanks!
James Buchanan


             reply	other threads:[~2003-02-02 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 13:19 James Buchanan [this message]
     [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

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=5.1.0.14.0.20030203000618.00a0eb20@pop.iprimus.com.au \
    --to=jamesbuch@iprimus.com.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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

all inboxes | Powered by JetHome®