lkml.org 
[lkml]   [2001]   [Jul]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [RFC] I/O Access Abstractions
    Date
    From
    > Because if we just pass in this one extra piece of information which is
    > normally already available in the driver, we can avoid a whole lot of ugly
    > cruft in the out-of-line functions by plugging in the correct out-of-line
    > function to match the resource.

    Case 1:
    You pass a single cookie to the readb code
    Odd platforms decode it

    Case 2:
    You carry around bus number information all throughout
    each driver
    You keep putting it on/off the stack
    You keep it in structures
    You do complex generic locking for hotplug 'just in case'


    I think I prefer case 1.

    -
    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-03-22 12:55    [W:0.032 / U:30.272 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site