From: Yannis via Bugspray Bot <bugbot@kernel.org>
To: linux-mmc@vger.kernel.org, ulf.hansson@linaro.org
Subject: Re: RTS5229 built in card reader not detected after Linux 5.0.x
Date: Wed, 22 Jan 2025 15:45:28 +0000 [thread overview]
Message-ID: <20250122-b204003c22-2ed81898193b@bugzilla.kernel.org> (raw)
In-Reply-To: <20250122-b204003c0-5776b9acf361@bugzilla.kernel.org>
Yannis writes via Kernel.org Bugzilla:
Hi,
Since my comment above, I've moved to Ubuntu 20.10 which uses kernel 5.8. It looks like it's going to be a couple of weeks before Ubuntu reaches 5.8.18 so I can't confirm 100% that the problem is fixed yet.
However, as the kernel code change is the same as Chris' patch I can't see why it wouldn't work.
Scott, Chris' patch just prevents the SD card reader from being powered down and this is working in your case. The error message seems to point to an incompatibility between your card and the reader. I haven't had this problem with the NUC but other, older, machines have trouble reading my high speed/capacity cards.
View: https://bugzilla.kernel.org/show_bug.cgi?id=204003#c22
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
next prev parent reply other threads:[~2025-01-22 15:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 15:45 RTS5229 built in card reader not detected after Linux 5.0.x josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` David Lindstrom via Bugspray Bot
2025-01-22 15:45 ` David Lindstrom via Bugspray Bot
2025-01-22 15:45 ` David Lindstrom via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` Scott Brown via Bugspray Bot
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot
2025-01-22 15:45 ` Yannis via Bugspray Bot
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot
2025-01-22 15:45 ` Scott Brown via Bugspray Bot
2025-01-22 15:45 ` Scott Brown via Bugspray Bot
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot
2025-01-22 15:45 ` Yannis via Bugspray Bot [this message]
2025-01-22 15:45 ` Scott Brown via Bugspray Bot
2025-01-22 15:45 ` Doug Miles via Bugspray Bot
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot
2025-01-22 15:45 ` i.chryssochoos via Bugspray Bot
2025-01-22 15:45 ` Roger Heflin via Bugspray Bot
2025-01-22 15:45 ` Michael Garofalo via Bugspray Bot
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=20250122-b204003c22-2ed81898193b@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/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