From: "Garrett D'Amore" <garrett@damore.org>
To: Pierre Ossman <pierre@ossman.eu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
sdhci-devel@lists.ossman.eu,
Maxim Levitsky <maximlevitsky@gmail.com>,
Robert Hancock <hancockrwd@gmail.com>
Subject: Re: [Sdhci-devel] SDHCI driver runnining in aspire one, allows to write to R/O SD cards
Date: Sun, 03 May 2009 13:42:53 -0700 [thread overview]
Message-ID: <49FE01CD.8000903@damore.org> (raw)
In-Reply-To: <20090503212944.214d7137@mjolnir.ossman.eu>
Pierre Ossman wrote:
> On Mon, 27 Apr 2009 11:12:13 -0700
> Garrett D'Amore <garrett@damore.org> wrote:
>
>
>> As an extra data point, my sdhost driver in OpenSolaris works fine on
>> the AA1.. it does see that the cards are locked, and refuses to allow
>> them to be mounted read/write.
>>
>> This leads me to believe that the original linux problem is one of two
>> things:
>>
>> * either a bug in the linux code, or
>> * busted circuit/hardware on a specific unit (i.e. a damaged unit)
>>
>>
>
> I don't suppose you could try a Linux LiveCD to determine if your AA1
> has the same issue under Linux?
>
I'll have to download one, and I need to install via USB media... (which
I've not done with Linux before) -- the AA1 doesn't have a CDROM drive.
- Garrett
> Rgds
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> sdhci-devel mailing list
> sdhci-devel@lists.ossman.eu
> http://list.drzeus.cx/mailman/listinfo/sdhci-devel
>
prev parent reply other threads:[~2009-05-03 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 9:29 SDHCI driver runnining in aspire one, allows to write to R/O SD cards Maxim Levitsky
2009-04-20 23:42 ` Robert Hancock
2009-04-23 22:10 ` Maxim Levitsky
2009-04-26 15:21 ` Maxim Levitsky
2009-04-27 18:12 ` [Sdhci-devel] " Garrett D'Amore
2009-04-27 19:07 ` Maxim Levitsky
2009-04-27 22:13 ` Garrett D'Amore
2009-05-03 19:29 ` Pierre Ossman
2009-05-03 20:42 ` Garrett D'Amore [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=49FE01CD.8000903@damore.org \
--to=garrett@damore.org \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=pierre@ossman.eu \
--cc=sdhci-devel@lists.ossman.eu \
/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;
as well as URLs for NNTP newsgroup(s).