lkml.org 
[lkml]   [2005]   [Sep]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 2.6.13 2/14] sas-class: README
    Luben Tuikov wrote:
    > Signed-off-by: Luben Tuikov <luben_tuikov@adaptec.com>

    <snip>

    An interesting document. I have a small quibble here (and a larger
    one about the SMP user space access that I will elaborate on
    in a day or so).

    > +Port events, passed on a _phy_:
    > + PORTE_BYTES_DMAED, (M)
    > + PORTE_BROADCAST_RCVD, (E)
    > + PORTE_LINK_RESET_ERR, (C)
    > + PORTE_TIMER_EVENT, (C)
    > + PORTE_HARD_RESET.

    Link layer broadcasts don't only come from expanders
    (i.e. BROADCAST(CHANGE) ); SAS 1.1 (sas1r09e.pdf) defines
    BROADCAST(SES) coming from a target port associated with
    an enclosure device (SES peripheral type). It is not
    clear to me how the associated primitive is conveyed back
    with the broadcast.

    If it is not conveyed back then perhaps that broadcast define
    could be expanded to:
    PORTE_BROADCAST_CHANGE (E)
    PORTE_BROADCAST_SES (Target)

    and a note inserted that BROADCAST(RESERVED CHANGE 0) and
    BROADCAST(RESERVED CHANGE 1) be mapped to PORTE_BROADCAST_CHANGE
    by the LLDD as per table 79 of sas1r09e.pdf .

    BTW table 70 indicates an initiator can originate a BROADCAST(CHANGE),
    not just an expander.

    Doug Gilbert
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-09-11 03:47    [W:5.997 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site