From: Dan Malek <dan@mvista.com>
To: Ron Bianco <ronb@junction.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: A stable linux 2.2.xx for sandpoint-8240 anywhere?
Date: Fri, 29 Dec 2000 16:52:30 -0500 [thread overview]
Message-ID: <3A4D079E.1778BCEC@mvista.com> (raw)
In-Reply-To: 000501c071cd$44356c00$4d012ac7@warp-speed
Ron Bianco wrote:
> There are problems as this port was based on an experimental and unstable
> kernel.
> There are patches (tons) that fix some of the problems we've been seeing,
Really? Although not suitable for a product, there shouldn't be "tons"
of patches required to make it useful in a development environment.
There may be patches required to work around the different revisions
of the Sandpoint hardware.
> We're facing a deadline and must concentrate on a custom driver for now.
That is where all of the resources seem to be going right now, to
custom hardware. The 8240 is just a 603 with 106/107 OpenPIC PCI
bridge. The Sandpoint is what required all of the code changes. If
your hardware is like a Sandpoint, then there are still changes
required to suit your needs. Most people aren't building Sandpoint-like
hardware that I know about.
> Eventually we'll make our patches for 8240 available.
Do it quickly, as there will soon be 824x updates in the 2.4 kernel.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-29 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 19:26 A stable linux 2.2.xx for sandpoint-8240 anywhere? Ron Bianco
2000-12-29 19:36 ` Tom Rini
2000-12-29 21:52 ` Dan Malek [this message]
2000-12-29 23:31 ` Ron Bianco
2000-12-30 1:18 ` Dan Malek
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=3A4D079E.1778BCEC@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=ronb@junction.net \
/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.