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:	Tue, 15 Jul 2008 15:05:16 +0200
From:	Michael Buesch <mb@...sch.de>
To:	Ben Nizette <bn@...sdigital.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	David Brownell <david-b@...bell.net>,
	Piot Skamruk <piotr.skamruk@...il.com>,
	openwrt-devel@...ts.openwrt.org
Subject: Re: [PATCH] Add SPI over GPIO driver

On Tuesday 15 July 2008 07:30:51 Ben Nizette wrote:
> Looks good overall.  I'm not sure that it need pretend to be
> hotpluggable though

Because the hardware _is_ hotpluggable.

> (i.e. the board info can be hardwired so there's no 
> need for the board setup callback).

I'm not sure why we should limit ourselves so much by compiling
dynamic and completely individual information, like the bus
wireing into the kernel.
This _has_ to be dynamic, as the wireing is _completely_ random and
different for every machine. This is selfmade hardware. ;)

> What problem are you solving (or whole in board support are you
> plugging) in this dynamic plugging of MMCs?

This is to support running MMCs/SDs on GPIO pins.
Which board or card provides the GPIO pins doesn't matter. It doesn't
matter, as it's completely abstracted. You can even run 10 or more
of the cards at the same time, if you have enough GPIO pins.

Of course, this is mostly useful for embedded systems only.
But it is not bound to any specific type of hardware. The hardware just
has to implement generic GPIO for its GPIO pins.

-- 
Greetings Michael.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ