[lkml]   [2006]   [Oct]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: 2.6.19-rc1-mm1
    On 10/10/06, Andrew Morton <> wrote:
    > +# drivers-add-lcd-support.patch: Pavel says use fbcon
    > +drivers-add-lcd-support.patch
    > +drivers-add-lcd-support-update.patch

    Has the # a special meaning?

    I'm going to work on offering the fbcon feature as Pavel requested. We
    suggested 2 ways.

    Pavel's idea: Change the driver so the cfag12864b module will be just
    a framebuffer device, removing access through /dev/cfag12864b.

    My idea: Code a new module called "fbcfag12864b", which will depend on
    cfag12864b and will be the framebuffer device. This way we have both
    devices, and they doesn't affect each other as they are different
    things. So the ks0108 and cfag12864b can stay without any changes.
    Also, if we finally decide we don't want the raw cfag12864b module, it
    is easy to remove it from the cfag12864b and the fbcafg12864b will
    continue working.

    Is there anyone who can decide which idea is better? If not, I will
    code it my way. Also, if the Pavel's idea will be the chosen one, it
    will be easier to put the fbcfag12864b code into the cfag12864b rather
    than the opposite.
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-10-10 09:33    [W:0.032 / U:13.328 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site