From: Dan Malek <dan@netx4.com>
To: Cort Dougan <cort@fsmlabs.com>
Cc: rodgersg@us.ibm.com, linuxppc-dev@lists.linuxppc.org,
bh40@calva.net, paulus@linuxcare.com, geert@linux-m68k.org,
paubert@iram.es, dburcaw@terraplex.com, hollis@linuxppc.com,
drdoc@netcene.com, gdt@linuxppc.org, dan_bethe@yahoo.com,
khendricks@ivey.uwo.ca, tgall@us.ibm.com,
trini@kernel.crashing.org, jcarr@linuxppc.com,
jhaas@linuxppc.com, devel@yellowdoglinux.com, tomcook@us.ibm.com
Subject: Re: PowerPC BOF at Ottawa Linux Symposium July 19
Date: Mon, 12 Jun 2000 15:29:20 -0400 [thread overview]
Message-ID: <39453A10.55C5F4D6@embeddededge.com> (raw)
In-Reply-To: 20000610182014.H31097@medea.fsmlabs.com
Cort Dougan wrote:
>
> I won't be in Ottawa but I have a suggestion for something to talk about
> there if anyone would be interested in it. Could you have a brainstorming
> session about how to re-structure the chip/architecture portions of
> arch/ppc/?
I don't know if I will be there, but I would like to make a comment
on this as well. The BOF started as a workstation/server discussion,
and the chip/architecture issues are really the result of the variety
of embedded PowerPC processors and boards.
There is PREP/CHRP/PowerMac that you have successfully combined, with
minor configuration differences among all of them. Then we have lots
of different PowerPC cores with highly integrated functional units on
a variety of different board configurations. I think we are fortunate
to be able to provide this wide range of solutions, but it does present
the source code structure challenge as Cort (and others) have discussed.
As a workstation/server BOF, I don't know how much interest exists to
discuss this. The easy answer is a set of orthogonal directory trees,
but I think the highest priority should be on maintaining a set of
common files. Having experienced splitting some processor dependent
files, I would still take the #ifdefs over tracking similar changes
across multiple files.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-12 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-09 19:03 PowerPC BOF at Ottawa Linux Symposium July 19 rodgersg
2000-06-11 0:20 ` Cort Dougan
2000-06-12 19:29 ` Dan Malek [this message]
2000-06-13 10:33 ` Adrian Cox
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=39453A10.55C5F4D6@embeddededge.com \
--to=dan@netx4.com \
--cc=bh40@calva.net \
--cc=cort@fsmlabs.com \
--cc=dan_bethe@yahoo.com \
--cc=dburcaw@terraplex.com \
--cc=devel@yellowdoglinux.com \
--cc=drdoc@netcene.com \
--cc=gdt@linuxppc.org \
--cc=geert@linux-m68k.org \
--cc=hollis@linuxppc.com \
--cc=jcarr@linuxppc.com \
--cc=jhaas@linuxppc.com \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
--cc=paulus@linuxcare.com \
--cc=rodgersg@us.ibm.com \
--cc=tgall@us.ibm.com \
--cc=tomcook@us.ibm.com \
--cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.