public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Luca Risolia <luca.risolia@studio.unibo.it>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk, luc@saillard.org
Subject: Re: Linux 2.6.9-ac3
Date: Mon, 25 Oct 2004 18:22:21 -0400	[thread overview]
Message-ID: <417D7C9D.8040409@tmr.com> (raw)
In-Reply-To: <20041023193651.1cbcb80d.luca.risolia@studio.unibo.it>

Luca Risolia wrote:
> On Sat, 23 Oct 2004 10:54:25 -0400
> Bill Davidsen <davidsen@tmr.com> wrote:
> 
> 
>>Luca Risolia wrote:
>>
>>>>o       Restore PWC driver                              (Luc Saillard)
>>>
>>>
>>>This driver does decompression in kernel space, which is not
>>>allowed. That part has to be removed from the driver before
>>>asking for the inclusion in the mainline kernel.
>>
>>What do you mean by "not allowed?"
> 
> 
> http://marc.theaimsgroup.com/?l=linux-video&m=108627734619978&w=2
> 
> Also note how Alan Cox seems not to be actually coherent with his
> previous opinions.

If you're a Republican he's "wishy-washy", if you're a Democrat he's 
"flexible and adaptable to changing conditions." If you're not a US 
resident you're confused by the previous sentence, please ignore it's an 
in-joke (or tragedy).
> 
>  Clearly it would nice if it were in 
> 
>>user space, but it would have to be in EVERY user application to be 
>>useful. We have compression in kernel for ppp, and there's only one 
>>significant use for that, requiring that every application support every 
>>vendor hardware makes it a non-scalable NxM problem.
> 
> 
> Hmm..What about a common library finally?

That sounds like the eventual solution. A vendor to common format 
conversion library, and with luck someone will be clever and let the 
driver select it in a nice acceptable way. Thought: after open an ioctl 
to tell you which conversion to use? The optimal mechanics are 
inobvious, but I think the library is the right idea.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  reply	other threads:[~2004-10-25 23:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22  8:13 Linux 2.6.9-ac3 Luca Risolia
2004-10-22  9:21 ` Luc Saillard
2004-10-22 12:30   ` Luca Risolia
2004-10-22 12:34     ` Xavier Bestel
2004-10-22 13:33       ` Luc Saillard
2004-10-22 14:22         ` Ronald S. Bultje
2004-10-22 14:38         ` David Weinehall
2004-10-22 14:15       ` Gergely Nagy
2004-10-22 13:16     ` Luc Saillard
2004-10-22 14:07       ` Luca Risolia
2004-10-22 14:10     ` Gerd Knorr
2004-10-22 15:51       ` Alan Cox
2004-10-22 18:14         ` Gerd Knorr
2004-10-23 13:41           ` Luca Risolia
2004-10-22 11:09 ` Alan Cox
2004-10-22 13:00   ` Luca Risolia
2004-10-22 15:49     ` Alan Cox
2004-10-23 14:54 ` Bill Davidsen
2004-10-23 17:36   ` Luca Risolia
2004-10-25 22:22     ` Bill Davidsen [this message]
2004-10-26  5:29       ` Luc Saillard
  -- strict thread matches above, loose matches on Subject: below --
2004-10-21 23:08 Alan Cox
2004-10-22  0:59 ` Mark Lord
2004-10-22  1:18 ` Con Kolivas
2004-10-22  6:36 ` Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=417D7C9D.8040409@tmr.com \
    --to=davidsen@tmr.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc@saillard.org \
    --cc=luca.risolia@studio.unibo.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox