All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: Kumar Gala <kumar.gala@freescale.com>,  linuxppc-embedded@ozlabs.org
Subject: Re: What ethernet driver to use in 2.6.8.1 instead of gianfar in 2.6.11.x?
Date: Tue, 17 May 2005 18:45:00 +0200	[thread overview]
Message-ID: <428A1F8C.10903@anagramm.de> (raw)
In-Reply-To: <a659357b80a843e5eb3db2ebd5ec3c53@freescale.com>

Hello, Kumar!

 >> for some tests and glibc-builds I want to work with a 2.6.8.1 kernel
 >>  temporarily on a freescale mpc8540.
 >
 > Out of interest, what issues did you have with 2.6.11.x?

I want to see if I can get more details out of failing glibc-2.3.{4,5} ntpl
tests on a running system. That's not related to anything mpc85xx specific.

I'll take the gianfar if necessary.
(Or I just plug a rtl8139 into pci... and go with that)
The .config is not an issue, then. Thanks!

Greets,

Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19


Kumar Gala wrote:
>> In 2.6.8.1 there was no gianfar ethernet driver. Is it okay to use the
>>  fec drivers instead of the gianfar or is it better to put the gianfar
>>  drivers back into 2.6.8.1? (100Mbps are okay for that testing)
> 
> 
> I doubt fec drivers would ever work for the TSECs.  You should be able 
> to pull the driver code out of 2.6.11.x for gianfar back into 2.6.8.1 
> w/o any real issue.
> 
>> Maybe somebody can get me a working .config for 2.6.8.1 and mpc8540ads?
> 
> 
> Can you start with the .config file that exists in the 2.6.11 ?
> 
> - kumar
> 
> 

      reply	other threads:[~2005-05-17 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17 11:56 What ethernet driver to use in 2.6.8.1 instead of gianfar in 2.6.11.x? Clemens Koller
2005-05-17 15:41 ` Kumar Gala
2005-05-17 16:45   ` Clemens Koller [this message]

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=428A1F8C.10903@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-embedded@ozlabs.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 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.