From: Jamie Heilman <jamie@audible.transient.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: BriQ & Linux 2.6
Date: Fri, 21 May 2004 23:45:21 -0700 [thread overview]
Message-ID: <20040522064520.GM8520@audible.transient.net> (raw)
In-Reply-To: <1085199239.9230.4.camel@gaston>
Benjamin Herrenschmidt wrote:
>
> Well... the base clock isn't what the driver thinks, so it must be
> hacked. But the driver doesn't provide a clean way to set another
> base clock, I'm trying to find something better than what the hack
> in the patch does.
Well progress so far, I have 2.6.6 booting now, had to fumble a little
to apply one chunk but the rest was easy. Problems so far: during the
entire boot, my console is line-noise-like hash[1], until runlevel 2,
then it starts behaving correctly. The NICs (I have the PCI
expansion + extra NIC board) are having some issues....
RX packets:118521 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:57244 dropped:0 overruns:0 carrier:57244
...and yet, strangly I don't seem to be having any obvious network
performance problems.
Now this isn't the first time I've had issues with either of those,
and I think there are some patches in the Total Impact kernel source
for the NIC issue. So I'm definately a lot closer than I was.
--
Jamie Heilman http://audible.transient.net/~jamie/
"...thats the metaphorical equivalent of flopping your wedding tackle
into a lion's mouth and flicking his lovespuds with a wet towel, pure
insanity..." -Rimmer
[1] like all: x<��x�x��x��x��x�x��x<�x�x
but then all the kernels from Total Impact do the same thing, and
I bet if I remove the base clock hack it will just work. Or
atleast appear to just work. Sometimes I wonder if my BriQ is
cursed.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-22 6:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 7:40 BriQ & Linux 2.6 Jamie Heilman
2004-05-21 23:10 ` Benjamin Herrenschmidt
2004-05-21 23:35 ` Jamie Heilman
2004-05-22 4:14 ` Benjamin Herrenschmidt
2004-05-22 6:45 ` Jamie Heilman [this message]
2004-05-22 7:12 ` Benjamin Herrenschmidt
2004-05-22 19:36 ` Jamie Heilman
2004-05-24 6:47 ` Jamie Heilman
2004-05-25 23:30 ` Benjamin Herrenschmidt
2004-05-26 0:00 ` Jamie Heilman
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=20040522064520.GM8520@audible.transient.net \
--to=jamie@audible.transient.net \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@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).