From: Steven Hein <ssh@sgi.com>
To: dan@netx4.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: ppc.kernel.org problems
Date: Mon, 03 Apr 2000 07:06:32 -0500 [thread overview]
Message-ID: <38E88948.DE0DB79B@sgi.com> (raw)
Dan,
(My apologies if I'm not reading this right......)
I just updated from BitKeeper this morning, and I'm still seeing
problems.....
- in arch/ppc/8xx_io/uart.c the version says 0.02, where the version
in the HardHat tree is 0.03
- the arch/ppc/8xx_io/fec.c still won't compile for me; it is trying to
reference the field 'tbusy' in struct net_device, and there is no
'tbusy' field in net_device (looks like this still coresponds to the
older 'struct device', which did have a 'tbusy' field.....)
Thanks,
Steve
Dan Malek wrote:
>
> I am working on the 2.3.xx kernel right now. There have been lots of
> generic changes that need integration for 8xx. Keep looking at the
> tree over the next few days, it should come together.
>
> > I have BitKeeper access and I grabbed the latest Linux/PPC kernel tree,
> > but it doesn't have updated FEC or UART drivers in arch/ppc/8xx_io,
>
> That should have all been there last week......
>
>
> -- Dan
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steve Hein (ssh@sgi.com) Engineering Diagnostics/Software
Silicon Graphics, Inc.
1050 Lowater Road Phone: (715) 726-8410
Chippewa Falls, WI 54729 Fax: (715) 726-6715
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-04-03 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-03 12:06 Steven Hein [this message]
2000-04-03 19:59 ` ppc.kernel.org problems Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2000-03-23 15:22 Steven Hein
2000-03-27 18:50 ` 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=38E88948.DE0DB79B@sgi.com \
--to=ssh@sgi.com \
--cc=dan@netx4.com \
--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).