From: Pantelis Antoniou <panto@intracom.gr>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: rdiz@alumni.deec.uc.pt,
Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 2.6-7-rc1 8xx - No go
Date: Fri, 28 May 2004 15:59:54 +0300 [thread overview]
Message-ID: <40B737CA.6080205@intracom.gr> (raw)
In-Reply-To: <Pine.LNX.4.58.0405280812580.14722@localhost.localdomain>
Robert P. J. Day wrote:
>On Fri, 28 May 2004 rdiz@alumni.deec.uc.pt wrote:
>
>
>>Did you actually manage to compile standard (no tweak), 2.6.7-rc1 for 8xx?
>>If so, what '8xx Machine Type' did you chose?
>>
>
>and here's another almost assuredly dumb question on my part -- can
>someone clarify the different kernel source trees that are under
>discussion here?
>
I could try but I'm not insane yet :). Tom?
>
>the one i'm playing with is ppc.bkbits.net:8080/linuxppc-2.5, while the
>posting above suggests a recent version straight from the stock kernel.org
>repository.
>
that's the one I working one too.
>
>what's the protocol for patches and updates? do first attempts at patches
>go into the 2.5 tree and, from there, get pushed up to the stock tree?
>just curious about the proper way i should be updating my source tree and
>testing.
>
>thanks.
>
>rday
>
>
>
>
>
Regards
Pantelis
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-28 12:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 8:40 2.6-7-rc1 8xx - No go Pantelis Antoniou
2004-05-28 10:17 ` Pantelis Antoniou
2004-05-28 11:38 ` rdiz
2004-05-28 12:16 ` Robert P. J. Day
2004-05-28 12:59 ` Pantelis Antoniou [this message]
2004-05-28 12:24 ` Pantelis Antoniou
2004-05-28 12:38 ` RTC no longer exist on the 866/87x/88x David Ho
2004-05-28 12:45 ` Pantelis Antoniou
2004-05-28 13:29 ` Mark Chambers
2004-05-28 23:23 ` 2.6-7-rc1 8xx - No go Paul Mackerras
2004-05-28 23:43 ` Tom Rini
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=40B737CA.6080205@intracom.gr \
--to=panto@intracom.gr \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rdiz@alumni.deec.uc.pt \
--cc=rpjday@mindspring.com \
/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).