Drive emulation at driver level

Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I would like to emulate a virtual SED at driver level. The goal is to develop/simulate the "firmware" of a drive, and map driver interface commands to an app which would handle interface specific commands. The driver interface may be one of SCSI, ATA, NVME.
Any hint how to create such an ATA/SCSI/... device, and how to map accesses to a userland app (such as nbd, but at device interface level)?
drivers devices scsi sata
add a comment |Â
up vote
1
down vote
favorite
I would like to emulate a virtual SED at driver level. The goal is to develop/simulate the "firmware" of a drive, and map driver interface commands to an app which would handle interface specific commands. The driver interface may be one of SCSI, ATA, NVME.
Any hint how to create such an ATA/SCSI/... device, and how to map accesses to a userland app (such as nbd, but at device interface level)?
drivers devices scsi sata
The source code of SATA kernel driver sounds like the natural starting point. That's where I would look.
â ajeh
Jun 28 at 17:21
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I would like to emulate a virtual SED at driver level. The goal is to develop/simulate the "firmware" of a drive, and map driver interface commands to an app which would handle interface specific commands. The driver interface may be one of SCSI, ATA, NVME.
Any hint how to create such an ATA/SCSI/... device, and how to map accesses to a userland app (such as nbd, but at device interface level)?
drivers devices scsi sata
I would like to emulate a virtual SED at driver level. The goal is to develop/simulate the "firmware" of a drive, and map driver interface commands to an app which would handle interface specific commands. The driver interface may be one of SCSI, ATA, NVME.
Any hint how to create such an ATA/SCSI/... device, and how to map accesses to a userland app (such as nbd, but at device interface level)?
drivers devices scsi sata
edited Jul 11 at 13:49
asked Jun 28 at 10:45
A.B.
64
64
The source code of SATA kernel driver sounds like the natural starting point. That's where I would look.
â ajeh
Jun 28 at 17:21
add a comment |Â
The source code of SATA kernel driver sounds like the natural starting point. That's where I would look.
â ajeh
Jun 28 at 17:21
The source code of SATA kernel driver sounds like the natural starting point. That's where I would look.
â ajeh
Jun 28 at 17:21
The source code of SATA kernel driver sounds like the natural starting point. That's where I would look.
â ajeh
Jun 28 at 17:21
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f452406%2fdrive-emulation-at-driver-level%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
The source code of SATA kernel driver sounds like the natural starting point. That's where I would look.
â ajeh
Jun 28 at 17:21