From: Christian Zankel <chris@mvista.com>
To: Dan Malek <dan@netx4.com>
Cc: cort@fsmlabs.com, linuxppc-dev@lists.linuxppc.org,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: bootloader & head.S weirdness & restructuring
Date: Tue, 23 Nov 1999 10:22:47 -0800 [thread overview]
Message-ID: <383ADB77.C06460C4@mvista.com> (raw)
In-Reply-To: 383A3610.BF976EDF@netx4.com
Hi Dan,
Dan Malek wrote:
> Cort Dougan wrote:
> > Yes, I do walk along that path quite often :)
> > } head.S. (Try to walk along the 'path' of the 8xx implementation).
>
> OK, I am a little clueless at this hour. As it appears you are
> making fun of the way I wrote that code, perhaps you should
> provide a suggestion. I have more, the 82xx looks just like
> that :-)......I am off to look at the m68k tree......
I'm sorry, I didn't want to make fun or criticize any of you. In fact, I
think you did a very good job. And I don't want to touch most of the
code at all. I just would like to rearrange them slightly. So, what I
wanted to say is, that when I first brought up linux on that board I
went through several files and whenever I found a #if(n)def CONFIG_8xx I
knew that I had to add another condition. That was what I meant with
'walking along the patch of the 8xx implementation'. However, that might
end up in having very long lines like this one
#if (CONFIG_8xx = 1) || (CONFIG_BOARDA = 1) || CONFIG_BOARD_C = 1) [...]
at several positions in several files.
So, basically, what I wanted to ask you about, is, what you think about
rearranging some small part of the sources into dedicated machine
dependent files and if it is doable and if you know of any constraints
about the way to do it. Or, if you would suggest just to add another
machine into the current code.
Thanks,
Christian
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-11-23 18:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-22 11:04 bootloader & head.S weirdness Benjamin Herrenschmidt
1999-11-22 21:37 ` Cort Dougan
1999-11-22 23:17 ` bootloader & head.S weirdness & restructuring Christian Zankel
1999-11-22 23:55 ` Cort Dougan
1999-11-23 3:31 ` Christian Zankel
1999-11-23 3:40 ` Cort Dougan
1999-11-23 6:37 ` Dan Malek
1999-11-23 18:22 ` Christian Zankel [this message]
1999-11-23 20:20 ` Dan Malek
1999-11-25 17:13 ` Geert Uytterhoeven
1999-11-25 19:49 ` Dan Malek
1999-11-26 9:06 ` Geert Uytterhoeven
1999-11-26 9:42 ` Michael Schmitz
1999-11-26 12:06 ` Wolfgang Denk
1999-11-28 22:41 ` Dan Malek
1999-11-29 7:12 ` Geert Uytterhoeven
1999-11-23 16:12 ` Michael Schmitz
1999-11-23 16:17 ` David Edelsohn
1999-11-23 17:46 ` Cort Dougan
1999-11-23 16:15 ` Gabriel Paubert
1999-11-23 16:52 ` Marcus Sundberg
1999-11-23 17:01 ` Gabriel Paubert
1999-11-23 17:45 ` Cort Dougan
1999-11-23 10:35 ` bootloader & head.S weirdness Benjamin Herrenschmidt
1999-11-23 10:50 ` Momchil Velikov
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=383ADB77.C06460C4@mvista.com \
--to=chris@mvista.com \
--cc=cort@fsmlabs.com \
--cc=dan@netx4.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-embedded@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).