From: Paul Mackerras <paulus@samba.org>
To: benh@kernel.crashing.org
Cc: Troy Benjegerdes <hozer@drgw.net>,
<linux-galileo@source.mvista.com>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: GT64260 merge warning
Date: Thu, 4 Apr 2002 08:11:02 +1000 (EST) [thread overview]
Message-ID: <15531.32246.283097.469203@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <20020402221544.21559@mailhost.mipsys.com>
benh@kernel.crashing.org writes:
> I'm almost done with the new bi_rec stuffs, I'll push it to _2_5
> this week as soon as I've tested a bit.
Interesting... I hope we're not going to end up with a lot of extra
complexity for not very much gain, though. If we are going to have a
more complex bi_rec setup, let's make sure that it is capable of
expressing a complete device tree. If not then I would prefer to see
a minimal amount of extra complexity.
In other words I think there are 2 tenable positions: the minimal one,
which just adds a BI_MAC_ADDR and maybe a BI_GT64260_ADDR tag to the
existing list of tags (and makes no change to the bi_rec structure),
and a full-featured one which allows for a tree of device records with
each device having a list of properties, each with a string name and
arbitrary binary data.
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-03 22:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 5:04 GT64260 merge warning Troy Benjegerdes
2002-04-03 6:23 ` Paul Mackerras
2002-04-02 22:15 ` benh
2002-04-03 22:11 ` Paul Mackerras [this message]
2002-04-03 8:53 ` benh
2002-04-03 19:24 ` Troy Benjegerdes
2002-04-03 6:47 ` Benjamin Herrenschmidt
2002-04-03 22:02 ` Paul Mackerras
2002-04-04 2:26 ` Dan Malek
2002-04-04 7:51 ` Geert Uytterhoeven
2002-04-04 17:06 ` [Linux-galileo] " Nye Liu
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=15531.32246.283097.469203@argo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=benh@kernel.crashing.org \
--cc=hozer@drgw.net \
--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).