lkml.org 
[lkml]   [2009]   [Aug]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH 1/3] SCSI: Allow platform-specific code to be run against the SCSI tree
    From
    Date
    On Mon, 2009-08-10 at 15:58 +0100, Matthew Garrett wrote:
    > On Mon, Aug 10, 2009 at 02:55:25PM +0000, James Bottomley wrote:
    > > On Mon, 2009-08-10 at 14:38 +0100, Matthew Garrett wrote:
    > > > On Mon, Jul 13, 2009 at 10:03:05PM +0100, Matthew Garrett wrote:
    > > > > In certain cases (such as ACPI) we want to be able to associate
    > > > > platform-specific data against the SCSI device tree. Handling this
    > > > > properly requires the ability to run platform code at SCSI init time.
    > > > > This patch adds stub functions that can be overridden if the platform
    > > > > defines CONFIG_SCSI_PLATFORM.
    > > >
    > > > James, any thoughts on this?
    > >
    > > Sorry, I'd thought this had all moved to libata so I'd stopped paying
    > > attention ... why are extra bits in SCSI necessary?
    >
    > They're SCSI as far as the device tree is concerned, so the glue
    > callbacks have to be registered from the SCSI layer. The only
    > implementation so far is for ACPI and only covers libata, but it could
    > potentially also be used to tie bay devices to the ofw tree on
    > openfirmware systems.

    It's hard for me to comment without seeing the scsi_platform_register
    code, but it strikes me that the only SCSI piece it's using is the
    scsi_bus ... what else is SCSI specific in there?

    James




    \
     
     \ /
      Last update: 2009-08-10 18:05    [W:0.019 / U:59.104 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site