On Mon, May 01, Alan Stern wrote:
> You could try running a 2.6.15 kernel with the clear_halt line removed.
This patch breaks it. I havent tried to put the code back into a 2.6.16 kernel.
.git/BISECT_LOG
git-bisect start
# good: [2b10839e32c4c476e9d94492756bb1a3e1ec4aa8] Linux v2.6.14
git-bise
On Mon, 1 May 2006, Olaf Hering wrote:
> On Mon, May 01, Alan Stern wrote:
>
> > I originally added the clear_halt just on a hunch. It seemed to help my
> > HP keyboard, but it caused problems for other people so I removed it
> > again. It turned out that the blacklist entry was enough to ma
On Mon, May 01, Alan Stern wrote:
> I originally added the clear_halt just on a hunch. It seemed to help my
> HP keyboard, but it caused problems for other people so I removed it
> again. It turned out that the blacklist entry was enough to make the HP
> keyboard work okay.
I havent looked,
On Mon, 1 May 2006, Olaf Hering wrote:
> On Wed, Jan 25, Alan Stern wrote:
>
> > My earlier experiment (adding a clear-halt for the interrupt-in endpoint)
> > failed. It turns out that it does cause problems for other devices. And
> > it wasn't needed anyway; a simple blacklist entry was eno
On Wed, Jan 25, Alan Stern wrote:
> My earlier experiment (adding a clear-halt for the interrupt-in endpoint)
> failed. It turns out that it does cause problems for other devices. And
> it wasn't needed anyway; a simple blacklist entry was enough to get my HP
> keyboard working.
>
> This pat
