From: Wolfgang Grandegger <wg@grandegger.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] e1000 problem @ current u-boot
Date: Thu, 03 Jul 2008 18:55:23 +0200 [thread overview]
Message-ID: <486D047B.5020904@grandegger.com> (raw)
In-Reply-To: <486CF2D6.3090805@matrix-vision.de>
Andre Schwarz wrote:
> Wolfgang,
>
> of course I meant no offense - of course your patch is harmless.
No problem.
> The System (network camera) is running for nearly 2 years now.
> Last working version has been u-boot 1.2.x with a 2.6.19 kernel.
>
> Since we've moved to the latest kernel we need a more recent u-boot.
>
> This is what I did - and e1000 no longer works.
>
> Of course I diff'ed the network stuff - no obvious changes at all.
> So I wonder if the problem is elsewhere and if e1000 is still working in
> general.
Have you read my previous mail? See below.
> Wolfgang Grandegger schrieb:
>> Andre Schwarz wrote:
>>> Wolfgang,
>>>
>>> as far as I can see on the list you sent the latest patches for the
>>> e1000 driver.
>> My patches just added some device ids,
>>
>>
>>> My e1000 (82541ER) stopped working on a MPC5200 based board with latest
>>> u-boot.
>>> I have a similar problem on another board ...
>>>
>>> Is your e1000 working properly on the latest u-boot ?
>> Yes, on a MPC8548 board. I have not tested it on the MPC5200.
>>
>>> Do I need any additional defines or environment settings to get it
>>> working again ?
>>>
>>> Obviously it is - again :-[ - my fault or is related to my build system.
>> I think there are some known problems with PCI on boards with a
>> MPC5200 Rev. A processor, e.g. my EEPRO100 card does not work on it.
>> What exactly does not work?
More information could be useful.
Wolfgang.
next prev parent reply other threads:[~2008-07-03 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 13:25 [U-Boot-Users] e1000 problem @ current u-boot Andre Schwarz
2008-07-03 15:29 ` Wolfgang Grandegger
2008-07-03 15:40 ` Andre Schwarz
2008-07-03 16:55 ` Wolfgang Grandegger [this message]
2008-07-03 21:03 ` André Schwarz
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=486D047B.5020904@grandegger.com \
--to=wg@grandegger.com \
--cc=u-boot@lists.denx.de \
/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.