From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] SATA: do not auto-initialize during boot
Date: Tue, 23 Dec 2008 00:51:42 -0500 [thread overview]
Message-ID: <200812230051.43923.vapier@gentoo.org> (raw)
In-Reply-To: <4941AD0A.40100@freescale.com>
On Thursday 11 December 2008 19:15:06 Scott Wood wrote:
> Mike Frysinger wrote:
> > On Thursday 11 December 2008 18:53:00 Wolfgang Denk wrote:
> >> And if they do, the code should fail gracefully, i. e. print some
> >> friendly error message like that S-ATA is not available.
> >
> > in this case, i think that's up to the controller. i.e. the controller
> > doesnt find anything and you get a message that nothing was found.
> >
> > i dont have a board to test with to know what will happen exactly, nor
> > does the current code make any statement that i can see. Scott ?
>
> IIUC, if it's "not available" the driver will still see the controller
> regs, but it will be trying to control pins that are actually routed to
> another device. That said, it should be the driver calling into
> SoC-specific code to find out, rather than a global SATA-blocker (what
> if a PCIe SATA card were used?).
i agree with that sentiment, but i'm not about to take on that restructure ;)
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20081223/995af0c1/attachment.pgp
next prev parent reply other threads:[~2008-12-23 5:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 8:04 [U-Boot] SATA/IDE/etc... init Mike Frysinger
2008-12-11 10:12 ` Wolfgang Denk
2008-12-11 10:32 ` [U-Boot] [PATCH] SATA: do not auto-initialize during boot Mike Frysinger
2008-12-11 16:17 ` Kumar Gala
2008-12-11 20:03 ` Mike Frysinger
2008-12-11 20:51 ` Kumar Gala
2008-12-11 20:56 ` Mike Frysinger
2008-12-11 21:01 ` Scott Wood
2008-12-11 21:07 ` Mike Frysinger
2008-12-11 21:16 ` Scott Wood
2008-12-11 21:24 ` Mike Frysinger
2008-12-11 21:36 ` Scott Wood
2008-12-11 22:06 ` Mike Frysinger
2008-12-11 23:57 ` Wolfgang Denk
2008-12-23 5:53 ` Mike Frysinger
2008-12-11 23:55 ` Wolfgang Denk
2008-12-11 23:53 ` Wolfgang Denk
2008-12-11 23:57 ` Mike Frysinger
2008-12-12 0:15 ` Scott Wood
2008-12-23 5:51 ` Mike Frysinger [this message]
2008-12-11 23:50 ` Wolfgang Denk
2008-12-11 23:49 ` Wolfgang Denk
2008-12-11 16:18 ` Kumar Gala
2008-12-11 20:02 ` Mike Frysinger
2008-12-11 23:18 ` Wolfgang Denk
2008-12-11 23:26 ` Kumar Gala
2008-12-12 0:01 ` Wolfgang Denk
2008-12-12 0:13 ` Kumar Gala
2008-12-11 12:47 ` [U-Boot] SATA/IDE/etc... init Mike Frysinger
2008-12-11 19:23 ` Scott Wood
2008-12-11 23:22 ` Wolfgang Denk
2008-12-11 23:48 ` Mike Frysinger
2008-12-11 23:51 ` [U-Boot] [PATCH v2] SATA: do not auto-initialize during boot Mike Frysinger
2008-12-12 0:16 ` Kumar Gala
2008-12-23 5:10 ` [U-Boot] [PATCH v3] " Mike Frysinger
2009-01-24 3:12 ` Mike Frysinger
2009-01-27 20:58 ` Wolfgang Denk
2009-01-27 21:12 ` [U-Boot] [PATCH v4] " Mike Frysinger
2009-01-27 22:43 ` Wolfgang Denk
2008-12-12 5:53 ` [U-Boot] SATA/IDE/etc... init Stefan Roese
2008-12-22 7:25 ` Mike Frysinger
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=200812230051.43923.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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