All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Clayton 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:20 +0000	[thread overview]
Message-ID: <20250122-b204003c14-66e8de5dc6a8@bugzilla.kernel.org> (raw)
In-Reply-To: <20250122-b204003c0-5776b9acf361@bugzilla.kernel.org>

Chris Clayton writes via Kernel.org Bugzilla:

I've reverted* bede03a579b3b4a036003c4862cc1baa4ddc351f and built the 5.4.0-40 kernel**.
The RTS5229 card reader in my NUC6CAYH now works with both SD and MMC cards.

* The commit does not revert cleanly because of some later changes. The manual fix up is not too difficult, however.

** Actually, the build fails but after the modules have been built so the rtsx_pci.ko driver module is available in the build directory. I installed it by hand and then ran depmod manually. The build system is a maze of voodoo that I am still trying to untangle to get a full set of deb files produced. Nevertheless, my testing strongly suggests that commit bede03a579b3b4a036003c4862cc1baa4ddc351f is the culprit.

I've also reverted the commit and built the resultant kernel on my (non-debian/ubuntu powered) laptop, which also has a card reader (RTL8411B PCI Express Card Reader) that needs this driver. That continues to work after he reversion.

View: https://bugzilla.kernel.org/show_bug.cgi?id=204003#c14
You can reply to this message to join the discussion.
-- 
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)


  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 [this message]
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
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-b204003c14-66e8de5dc6a8@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 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.