From: Tom Rini <trini@kernel•crashing.org>
To: Michael Sokolov <msokolov@ivan•Harhan.ORG>
Cc: linux-galileo@source•mvista.com, linuxppc-dev@lists•linuxppc.org
Subject: Re: [Linux-galileo] ev64260 bi_rec patch
Date: Mon, 1 Apr 2002 08:20:36 -0700 [thread overview]
Message-ID: <20020401152036.GA6360@opus.bloom.county> (raw)
In-Reply-To: <0203300045.AA13159@ivan.Harhan.ORG>
On Fri, Mar 29, 2002 at 04:45:43PM -0800, Michael Sokolov wrote:
>
> Mark A. Greer <mgreer@mvista•com> wrote:
>
> > Okay, the bi_recs need to be copied. Something for you to do over the weekend ;)
>
> I don't know how to do that in a way acceptable to you. I only know how to do
> things my way, which I've done in my patch which you've pocket-vetoed.
>
IIRC, your original patch did the parsing in parse_bootinfo() or so in
arch/ppc/kernel/setup.c which means each new driver bi_rec needs to
modify arch/ppc/kernel/setup.c, which isn't nice. What we need is
something like how we save Motorola residual data or bd_info stuffs
(memcpy in platform_init).
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-01 15:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-29 23:59 [Linux-galileo] ev64260 bi_rec patch Michael Sokolov
2002-03-29 22:24 ` Mark A. Greer
2002-03-29 22:30 ` Mark A. Greer
2002-03-29 22:41 ` Mark A. Greer
2002-03-30 0:45 ` Michael Sokolov
2002-04-01 15:20 ` Tom Rini [this message]
2002-04-01 15:25 ` Tom Rini
2002-04-01 15:09 ` Mark A. Greer
2002-04-01 18:53 ` Tom Rini
2002-04-01 19:52 ` Michael Sokolov
2002-04-01 20:21 ` Tom Rini
2002-04-02 2:38 ` Paul Mackerras
2002-04-02 2:50 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2002-03-30 0:42 Michael Sokolov
2002-04-01 19:31 Michael Sokolov
2002-04-01 18:03 ` Mark A. Greer
2002-04-01 20:09 Michael Sokolov
2002-04-02 3:35 Michael Sokolov
2002-04-03 5:09 ` Troy Benjegerdes
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=20020401152036.GA6360@opus.bloom.county \
--to=trini@kernel$(echo .)crashing.org \
--cc=linux-galileo@source$(echo .)mvista.com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=msokolov@ivan$(echo .)Harhan.ORG \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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