From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] cmd_ide: Fix detection problem with missing devices
Date: Thu, 14 May 2009 15:55:33 +0200 [thread overview]
Message-ID: <200905141555.33901.sr@denx.de> (raw)
In-Reply-To: <20090514134401.DC03E832E416@gemini.denx.de>
Hi Wolfgang,
On Thursday 14 May 2009 15:44:01 Wolfgang Denk wrote:
> > Currently only IDE busses are probed and all possible available devices
> > are listed in the IDE bootup log. Even when devices on the bus are not
> > available. This leads to the following output on the CPCI750:
> >
> > IDE: Bus 0: OK Bus 1: OK
> > Device 0: Model: HITACHI_DK23FA-20J Firm: 00M7A0A0 Ser#: 42D182
> > Type: Hard Disk
> > Capacity: 19077.1 MB = 18.6 GB (39070080 x 512)
> > Device 1: Model: Firm: Ser#:
> > Type: # 1F #
> > Capacity: not available
> > Device 2: Model: SanDisk SDCFB-128 Firm: vde 1.10 Ser#: gmo5i311404
> > Type: Removable Hard Disk
> > Capacity: 122.5 MB = 0.1 GB (250880 x 512)
> > Device 3: Model: Firm: Ser#:
> > Type: # 1F #
> > Capacity: not available
>
> If my understanding is correct, then this is a bug on your hardware.
I don't think so.
> > #endif
> > @@ -727,8 +728,12 @@ skip_bus:
> > if (!ide_bus_ok[IDE_BUS(i)])
> > continue;
> > ide_led(led, 1); /* LED on */
> > - ide_ident(&ide_dev_desc[i]);
> > + ret = ide_ident(&ide_dev_desc[i]);
> > ide_led(led, 0); /* LED off */
> > + if (ret < 0) {
> > + puts("not available\n");
> > + continue;
> > + }
>
> IIRC this should not be needed; normally, ide_bus_ok() should catch
> this.
No. ide_bus_ok() only checks the first drive/device on a bus. If this device
is ok, then all drives from this bus are printed.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2009-05-14 13:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 5:24 [U-Boot] [PATCH] cmd_ide: Fix detection problem with missing devices Stefan Roese
2009-05-14 13:44 ` Wolfgang Denk
2009-05-14 13:55 ` Stefan Roese [this message]
2009-05-14 14:59 ` Wolfgang Denk
2009-05-14 15:14 ` Stefan Roese
2009-05-14 20:54 ` Wolfgang Denk
2009-05-14 20:57 ` [U-Boot] [PATCH] IDE: bail out of dev_print() for unknow device types Wolfgang Denk
2009-05-14 20:59 ` [U-Boot] [PATCH v2] IDE: bail out of dev_print() for unknown " Wolfgang Denk
2009-05-15 5:27 ` Stefan Roese
2009-05-15 7:27 ` Wolfgang Denk
2009-05-15 7:33 ` Stefan Roese
2009-05-15 7:27 ` [U-Boot] [PATCH v3] " Wolfgang Denk
2009-05-15 20:30 ` Wolfgang Denk
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=200905141555.33901.sr@denx.de \
--to=sr@denx.de \
--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.