[lkml]   [2000]   [Aug]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Re: Move of input drivers, some word needed from you
> So, what does it boil down to? The need for an additional, well-defined
> interface, encapsulating and hiding common functions. Effectively, once

It isnt that simple

> the good interface is there, you will have an improved percentage of
> shared code. That's what Eric is after, you wrap it up nicely into a
> gift paper called interface.

You have to build -optional- interfaces. Instead of thinking about a layer
above the drivers think about a layer of support code _below_ the drivers
that can be shared and used when it fits. Now drivers that have odd needs
can skip pieces that dont fit. With a conventional view of layering they
end up fighting a pile of crap above them that does things they dont want
and eventually all the people trying to bend the layer above different ways
break it

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:37    [W:0.055 / U:0.536 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site