public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
* mmcoops + mmcblk
@ 2011-07-12  6:32 Simon Horman
  2011-07-14  4:28 ` Jaehoon Chung
  0 siblings, 1 reply; 2+ messages in thread
From: Simon Horman @ 2011-07-12  6:32 UTC (permalink / raw)
  To: linux-mmc
  Cc: Jaehoon Chung, Kyungmin Park, Chris Ball, Philip Rakity,
	'Andrew Morton', Matt Fleming

Hi,

I am looking over the "[RFC] mmcoops with panic/oops" and is strikes
me that although platform data is used to limit the area of the MMC
device to which the oops is witten, the entire device has to belong
(be bound to) the mmc_oops driver and as such no part of the device
can be used for anything else.

I am wondering if I am missing something?

In particular, I would like to allow a single MMC chip to be
used both by mmcblk (as a filesystem) and as mmc_oops (a small
area reserved for writing oops messages).


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-07-14  4:27 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-07-12  6:32 mmcoops + mmcblk Simon Horman
2011-07-14  4:28 ` Jaehoon Chung

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox