From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linux-galileo@source.mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: [Linux-galileo] ev64260 bi_rec patch
Date: Mon, 1 Apr 02 11:52:16 PST [thread overview]
Message-ID: <0204011952.AA28527@ivan.Harhan.ORG> (raw)
Tom Rini <trini@kernel.crashing.org> wrote:
> 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,
Yes.
> which isn't nice.
Agreed.
> What we need is
> something like how we save Motorola residual data or bd_info stuffs
> (memcpy in platform_init).
Both of those structures are fixed-length and are copied to static variables.
The bi_recs list has a variable length and can't be copied to a static variable
(unless we agree on a maximum size for it and make a static buffer of that
size, but someone other than me has to make that decision), and I don't know
how to make a dynamic memory allocation that early.
MS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev reply other threads:[~2002-04-01 19:52 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
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 [this message]
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=0204011952.AA28527@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
--cc=linux-galileo@source.mvista.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).