public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: Pat Gefre <pfg@sgi.com>,
	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 19:20:03 +0000	[thread overview]
Message-ID: <20040722192003.GA617@lnx-holt.americas.sgi.com> (raw)
In-Reply-To: <200407221357.53404.jbarnes@engr.sgi.com>

On Thu, Jul 22, 2004 at 01:57:53PM -0400, Jesse Barnes wrote:
> 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.

I am in the process of making this into four patches that will leave me with
a bootable system.  I need to test out the bte error handling code anyway.

The first patch will handle renaming the files, second and third are the
diffs_common* and then the fourth replaces the is the big patch.  I realize
this doesn't satisfy Christoph's request, but it is a first step.

Thanks,
Robin

  reply	other threads:[~2004-07-22 19:20 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
2004-07-22 19:20   ` Robin Holt [this message]
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=20040722192003.GA617@lnx-holt.americas.sgi.com \
    --to=holt@sgi.com \
    --cc=hch@infradead.org \
    --cc=jbarnes@engr.sgi.com \
    --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