linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Barbieri <barbieri@gmail.com>
To: Leigh Brown <leigh@solinno.co.uk>
Cc: Christoph Hellwig <hch@lst.de>,
	Sven Luther <sven.luther@wanadoo.fr>,
	debian-kernel@lists.debian.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: rs/6000 e30 + 240 (doral) support
Date: Thu, 29 Jul 2004 12:37:47 -0300	[thread overview]
Message-ID: <9ef20ef3040729083748c883c6@mail.gmail.com> (raw)
In-Reply-To: <2717.217.46.152.97.1091113282.squirrel@217.46.152.97>


On Thu, 29 Jul 2004 16:01:22 +0100 (BST), Leigh Brown
<leigh@solinno.co.uk> wrote:
> Christoph Hellwig said:
> >
> > On Thu, Jul 29, 2004 at 11:04:48AM -0300, Gustavo Barbieri wrote:
> >> > Most doesn't look too bad to me, but it's a lot of patches.  I vaguely
> >> > remember they were discussed on linuxppc-dev, so we should check the
> >> > comments over there.
> >>
> >> A lot of patches? Well, there is a lot of "code"... it's not really
> >> code, but just structure definitions... actually the patche touches
> >> the real code at few points, one it's just a null pointer checking,
> >> other are added cases to the switch statement so it can handle those
> >> boards, so I really can't a problem there.
> >>
> >> I already sent an email to linuxppc-dev in the past, but no replies:
> >>
> >> http://lists.linuxppc.org/linuxppc-dev/200407/msg00085.html
> >
> > Ah sorry, I confused it with Len's big IBM prep patchkit.  Except for a
> > tiny style issue this patch is fine with me.
> >
> > Any upstream comments as I'd hate to carry along a patch like that in
> > the Debian patchkit while we'd probably want it in Sarge.
> >
> > Gustavo, if we apply this patch you'll have to sign up for d-i testing
> > on prep, though ;-)
>
> I have a more comprehensive set of patches that remove the need for
> ugly hard-coded tables on RS/6000 PReP boxes, that I previously
> posted to linuxppc-dev.  I'll freshen them up tonight and post them
> again.  They provide generic support for the E20, E30, 140, 240, F30,
> and F40 and probably a few other ones that we don't know about, if
> we're lucky.  The F40 has problems but all the other work fine.


Hello Leigh,

Thanks for your original patch!

This patch you mean is the one in the TODO of those files? Using residual data?

--
Gustavo Sverzut Barbieri
---------------------------------------
Computer Engineer 2001 - UNICAMP
GPSL - Grupo Pro Software Livre
Cell..: +55 (19) 9165 8010
Jabber: gsbarbieri@jabber.org
  ICQ#: 17249123
   GPG: 0xB640E1A2 @ wwwkeys.pgp.net

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-07-29 15:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9ef20ef304071613494a0f0af9@mail.gmail.com>
     [not found] ` <20040717014441.GA13447@pegasos>
     [not found]   ` <20040729135130.GE19197@lst.de>
     [not found]     ` <9ef20ef3040729070439f6d8c1@mail.gmail.com>
2004-07-29 14:16       ` rs/6000 e30 + 240 (doral) support Christoph Hellwig
2004-07-29 14:24         ` Gustavo Barbieri
2004-07-29 15:18           ` Sven Luther
2004-07-29 15:34             ` Christoph Hellwig
2004-07-29 15:53             ` Gustavo Barbieri
2004-07-29 15:01         ` Leigh Brown
2004-07-29 15:37           ` Gustavo Barbieri [this message]
2004-07-29 21:14             ` Leigh Brown
2004-07-13 21:24 Gustavo Barbieri

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=9ef20ef3040729083748c883c6@mail.gmail.com \
    --to=barbieri@gmail.com \
    --cc=debian-kernel@lists.debian.org \
    --cc=hch@lst.de \
    --cc=leigh@solinno.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=sven.luther@wanadoo.fr \
    /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).