public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Bryan Wu <pwu@jadechip.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Does anyone use Lan91c96 in U-Boot?
Date: Wed, 7 Sep 2005 17:45:36 +0800	[thread overview]
Message-ID: <00e101c5b390$e610a440$27050a0a@jadechip.net> (raw)
In-Reply-To: 20050907085110.C1009352B3A@atlas.denx.de

Hi folks:

I use lan91c96 ethernet controller in my system board. And the Lan91c96 connects to my SoC by M68K bus.
Now I modified the original code to support the chip in U-Boot, U-Boot can download the kernel from networks by tftp.
But sometimes the kernel data is ok, sometimes the kernel data CRC error when I use bootm to bootup the kernel.

In the CRC error situation, U-Boot must think the kernel data downloaded from networks to RAM is ok, but the kernel decompressor
said it is CRC error.

Is there any idea for this? How to debug this?

Thanks a lot
Best Regards
Bryan Wu from China

  reply	other threads:[~2005-09-07  9:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 18:02 [U-Boot-Users] mtdparts Ladislav Michl
2005-09-06 19:47 ` Wolfgang Denk
2005-09-07  8:29   ` Ladislav Michl
2005-09-07  8:51     ` Wolfgang Denk
2005-09-07  9:45       ` Bryan Wu [this message]
2005-09-07 10:30     ` Andreas Engel
2005-09-07 12:54       ` Wolfgang Denk
2005-09-07 13:37         ` Ladislav Michl
2005-09-12 22:25           ` Wolfgang Denk
2005-09-13 15:00             ` Ladislav Michl
2005-09-15  8:49               ` [PATCH] voiceblue update (Re: [U-Boot-Users] mtdparts) Ladislav Michl
2006-07-22 19:05                 ` [U-Boot-Users] [PATCH] voiceblue update (Re: mtdparts) Wolfgang Denk
2006-07-25 15:00                   ` Ladislav Michl
2006-10-29 10:36                     ` Stefan Roese
2005-09-08 10:49         ` [U-Boot-Users] mtdparts Andreas Engel

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='00e101c5b390$e610a440$27050a0a@jadechip.net' \
    --to=pwu@jadechip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox