public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Pat Gefre <pfg@sgi.com>
Cc: linux-ia64@vger.kernel.org, hch@infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: Altix I/O code re-org
Date: Thu, 22 Jul 2004 17:57:53 +0000	[thread overview]
Message-ID: <200407221357.53404.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <200407221514.i6MFEVag084696@fsgi900.americas.sgi.com>

On Thursday, July 22, 2004 11:14 am, Pat Gefre wrote:
> We have redone the I/O layer in the Altix code.
>
> We are posting this code for review before submitting for
> inclusion in the 2.5 tree.
>
> The code can be seen at:
> ftp://oss.sgi.com/projects/sn2/sn2-update/
>
> The general changes are:
> o added new hardware support
> o ran all code thru Lindent
> o code cleanup (typedefs, include files, etc.)
> o simplified the directory structure (all files under arch/ia64/sn/io/
>   are deleted, new files are under arch/ia64/sn/ioif/)
> o code size reduced by >50%
> o major reorg of the code itself
> o copyright updates

One of the most important changes this patch makes is to rip out all of the 
SGI PCI probing code.  Our PROM now probes for I/O devices and tells the 
kernel where they are (similar to the ACPI model, which we may get to 
eventually).  The result is much more readable code with less duplication.  
Please take a look and let us know if you have any feedback, since we'd like 
to get this in as soon as we release a PROM that supports probing.

Thanks,
Jesse

  parent reply	other threads:[~2004-07-22 17:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22 15:14 Altix I/O code re-org Pat Gefre
2004-07-22 17:55 ` Christoph Hellwig
2004-07-22 17:57 ` Jesse Barnes [this message]
2004-07-22 19:20   ` Robin Holt
2004-07-22 19:40     ` Robin Holt
2004-07-22 19:42       ` Christoph Hellwig
2004-07-22 20:20         ` Robin Holt
2004-07-22 20:29       ` Robin Holt
2004-07-22 20:52         ` Robin Holt

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=200407221357.53404.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=hch@infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pfg@sgi.com \
    /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