On Saturday 22 September 2012 15:59:46 Pavel Herrmann wrote:
On Saturday 22 of September 2012 15:33:10 Marek Vasut wrote:
Dear Pavel Herrmann,
On Saturday 22 of September 2012 02:09:15 Marek Vasut wrote:
Dear Pavel Herrmann,
[...]
one or none - requests on USB
On Saturday 22 of September 2012 02:09:15 Marek Vasut wrote:
Dear Pavel Herrmann,
[...]
one or none - requests on USB flashes should not pass through
block_controller_driver.
Uh, what do they pass into then ?
their parent (an USB hub)
block_device instance (aka.
Dear Pavel Herrmann,
On Saturday 22 of September 2012 02:09:15 Marek Vasut wrote:
Dear Pavel Herrmann,
[...]
one or none - requests on USB flashes should not pass through
block_controller_driver.
Uh, what do they pass into then ?
their parent (an USB hub)
On Saturday 22 of September 2012 15:33:10 Marek Vasut wrote:
Dear Pavel Herrmann,
On Saturday 22 of September 2012 02:09:15 Marek Vasut wrote:
Dear Pavel Herrmann,
[...]
one or none - requests on USB flashes should not pass through
block_controller_driver.
On Thursday 20 of September 2012 21:58:17 Marek Vasut wrote:
Dear Pavel Herrmann,
This core will register all block devices (disk, cards, partitons) and
provide unfied access to them, instead of current method with device +
partition offset
Signed-off-by: Pavel Herrmann
Dear Pavel Herrmann,
On Thursday 20 of September 2012 21:58:17 Marek Vasut wrote:
Dear Pavel Herrmann,
This core will register all block devices (disk, cards, partitons) and
provide unfied access to them, instead of current method with device +
partition offset
On Friday 21 of September 2012 14:39:14 Marek Vasut wrote:
Dear Pavel Herrmann,
On Thursday 20 of September 2012 21:58:17 Marek Vasut wrote:
Dear Pavel Herrmann,
This core will register all block devices (disk, cards, partitons) and
provide unfied access to them, instead of
Dear Pavel Herrmann,
On Friday 21 of September 2012 14:39:14 Marek Vasut wrote:
Dear Pavel Herrmann,
On Thursday 20 of September 2012 21:58:17 Marek Vasut wrote:
Dear Pavel Herrmann,
This core will register all block devices (disk, cards, partitons)
and provide unfied
On Friday 21 of September 2012 15:53:26 Marek Vasut wrote:
Dear Pavel Herrmann,
On Friday 21 of September 2012 14:39:14 Marek Vasut wrote:
Dear Pavel Herrmann,
On Thursday 20 of September 2012 21:58:17 Marek Vasut wrote:
Dear Pavel Herrmann,
This core will register
Dear Pavel Herrmann,
[...]
blockctrl = AHCI, PIIX... whichever chip you have between SATA and PCI
(or generally disk-bus and board-bus)
So this is for sata ? Or will it also by used for SD/USB flash discs?
no, blockctrl will be used for SATA, PATA, SCSI, and anything of the sort
On Friday 21 of September 2012 17:34:27 Marek Vasut wrote:
Dear Pavel Herrmann,
[...]
blockctrl = AHCI, PIIX... whichever chip you have between SATA and PCI
(or generally disk-bus and board-bus)
So this is for sata ? Or will it also by used for SD/USB flash discs?
no,
Dear Pavel Herrmann,
On Friday 21 of September 2012 17:34:27 Marek Vasut wrote:
Dear Pavel Herrmann,
[...]
blockctrl = AHCI, PIIX... whichever chip you have between SATA and
PCI (or generally disk-bus and board-bus)
So this is for sata ? Or will it also by used for
On Friday 21 of September 2012 17:55:10 Marek Vasut wrote:
Dear Pavel Herrmann,
On Friday 21 of September 2012 17:34:27 Marek Vasut wrote:
Dear Pavel Herrmann,
[...]
blockctrl = AHCI, PIIX... whichever chip you have between SATA and
PCI (or generally disk-bus and
Dear Pavel Herrmann,
[...]
you should have a blockdev driver for USB flash and SD, but not
blockctrl
I'm lost again. Do I also need a blockdev driver for SATA controller now
that I need a blockdev driver for SD card controller ?
you need a blockdev for a blockctrl (see [5/11]),
On Friday 21 of September 2012 20:00:10 Marek Vasut wrote:
Dear Pavel Herrmann,
[...]
you should have a blockdev driver for USB flash and SD, but not
blockctrl
I'm lost again. Do I also need a blockdev driver for SATA controller now
that I need a blockdev driver for SD card
Dear Pavel Herrmann,
On Friday 21 of September 2012 20:00:10 Marek Vasut wrote:
Dear Pavel Herrmann,
[...]
you should have a blockdev driver for USB flash and SD, but not
blockctrl
I'm lost again. Do I also need a blockdev driver for SATA controller
now that I
On Friday 21 of September 2012 21:17:43 Marek Vasut wrote:
Dear Pavel Herrmann,
On Friday 21 of September 2012 20:00:10 Marek Vasut wrote:
Dear Pavel Herrmann,
[...]
you should have a blockdev driver for USB flash and SD, but not
blockctrl
I'm lost again.
Dear Pavel Herrmann,
[...]
I mean the particular block_controller_driver instance routes the
read/write block request from downstream block_device through
SATA/SD/SCSI/whatever library or layer back into itself. But the
later itself is the implementation of the library or layer API.
On Friday 21 of September 2012 23:11:57 Marek Vasut wrote:
Dear Pavel Herrmann,
[...]
I mean the particular block_controller_driver instance routes the
read/write block request from downstream block_device through
SATA/SD/SCSI/whatever library or layer back into itself. But the
Dear Pavel Herrmann,
[...]
one or none - requests on USB flashes should not pass through
block_controller_driver.
Uh, what do they pass into then ?
their parent (an USB hub)
block_device instance (aka. partition/disk) directly connected to USB hub
instance does not seem right.
This core will register all block devices (disk, cards, partitons) and provide
unfied access to them, instead of current method with device + partition offset
Signed-off-by: Pavel Herrmann morpheus.i...@gmail.com
---
Makefile | 1 +
drivers/blockdev/Makefile | 42
Dear Pavel Herrmann,
This core will register all block devices (disk, cards, partitons) and
provide unfied access to them, instead of current method with device +
partition offset
Signed-off-by: Pavel Herrmann morpheus.i...@gmail.com
---
Makefile | 1 +
22 matches
Mail list logo
