linux-kernel - Re: MMC: card test driver should not be builtin with other card support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 20 Jun 2008 19:08:33 +0200
From:	Pierre Ossman <drzeus-mmc@...eus.cx>
To:	Ben Dooks <ben-linux@...ff.org>
Cc:	linux-kernel@...r.kernel.org, Ben Dooks <ben-linux@...ff.org>
Subject: Re: MMC: card test driver should not be builtin with other card
 support

On Fri, 20 Jun 2008 12:01:15 +0100
Ben Dooks <ben-linux@...ff.org> wrote:

> On Fri, Jun 20, 2008 at 11:58:02AM +0100, ben@...ff.org.uk wrote:
> > The mmc test driver and mmc block driver will attempt to bind
> > to any card present in the system, which means only one of these
> > drivers will end up with the card. If either one of these is selected
> > as builtin, ensure the other does not get built.
> > 
> 
> This is what I would have liked to have done in Kconfig, but of course
> the system fails with a circular dependency error. Is there any way
> to get this done without some horrible hacks?
> 

AFAIK, you can manually control the driver binding using sysfs. Should
be solvable for the rootfs case using an initrd.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Use end-to-end encryption where
  possible.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/