Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Dominique Quatravaux <dom@idealx.com>
To: "Peter Horton" <phorton@bitbox.co.uk>, Stéphane <stf@c-gix.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Best kernel for a Cobalt Qube 2
Date: Tue, 30 Mar 2004 12:09:59 +0200	[thread overview]
Message-ID: <20040330100959.GA7466@idealx.com> (raw)
In-Reply-To: <40190154.10601@bitbox.co.uk>

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

Hello Stéphane, Peter and the list,

I'm replying to an old (Jan 2004) thread where the following messages
were exchanged:

[Stéphane]
> >I'm using a Cobalt Qube 2 for a long time now, it's under a 2.4.14 
> >kernel working 24/24 7/7 without any problem (no weird hang, no tulip 
> >problems, both internal network cards used).

[Peter]
> 2.4.23 is running solid here, but it needs a couple of patches (one 
> fixes a cache aliasing bug triggered by IDE in PIO mode, another fixes 
> up Galileo so the network driver works without stalling). I'll mail the 
> patches when I get home.

I'm interested in upgrading my RaQ2 kernel too. Would you be so kind
as to (re)post patches, URLs and success stories to me and/or the
list? (I will post a summary, and I can jot down a quick Web page for
the patches if needed). Thanks!

--
<< Tout n'y est pas parfait, mais on y honore certainement les jardiniers >>

			Dominique Quatravaux <dom@kilimandjaro.dyndns.org>



[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]

  reply	other threads:[~2004-03-30 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 11:11 Best kernel for a Cobalt Qube 2 Stéphane
2004-01-29 12:49 ` Peter Horton
2004-03-30 10:09   ` Dominique Quatravaux [this message]
2004-03-30 10:15     ` Peter Horton
2004-03-30 10:21       ` Kevin D. Kissell
2004-03-30 10:21         ` Kevin D. Kissell
2004-01-29 13:39 ` Brian Stratman

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=20040330100959.GA7466@idealx.com \
    --to=dom@idealx.com \
    --cc=linux-mips@linux-mips.org \
    --cc=phorton@bitbox.co.uk \
    --cc=stf@c-gix.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