On Thu, Oct 26, 2000 at 11:24:38PM +0200, Yoann Vandoorselaere wrote:
> Vojtech Pavlik <[EMAIL PROTECTED]> writes:
>
> > On Thu, Oct 26, 2000 at 11:05:04PM +0200, Yoann Vandoorselaere wrote:
> >
> > > yop, I 've done :
> > >
> > > ma
usbkbd, wacom and others
drivers/usb/wacom.c
Fix the Intuos 4DMouse and Intuos Lens tool behavior (James E. Blair)
The patch is against 2.4.0-test10-pre5.
TIA.
--
Vojtech Pavlik
SuSE Labs
diff -urN linux-test10-pre5-old/drivers/char/joystick/adi.c
linux/drivers/char/joystick/adi.c
n depends on both of the others unless you keep recompiling
> it
Not really, see for example ns558.c and adi.c plus their third module
gameport.c, all in drivers/char/joystick.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&quo
e, the impact of the failure on the chip is
permanent and stays till it's reprogrammed.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
gt; Are you sure there is not an error in the way the
> chipset is programmed ?
Which part of the chipset you mean? The PIT (programmable interrupt
timer)? That one is standard since XT times. The rest of the ISA bridge?
Maybe, but that's mostly BIOS work and shouldn't impact the PIT
u
r windows
> (thinking to the windows user base), VIA would be already in touch.
It can't happen under Windows, because Windows timer runs at 18 Hz
(timer programmed to 65535), while Linux uses 100 Hz (timer programmed
to approx 11920), so when the timer unprograms itself due to the bug to
6553
e code is the same all the time. Also, it happens both with
2.2 and 2.4 kernels ...
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
r.
I don't think so. If you check the code paths more closely, you'll see
that the timer is used even in the fast TSC case, the error causes by
too big 'count' variable propagates up to the TSC routine. That's where
I started hunting for the bug.
So no, it wasn't a place
months ago.
Ok, fixed in the CVS, a patch for the kernel to follow soon.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
d disks the one put on the secondary IDE channel has
> CHS=19857/16/63, no matter which one is, while the first one remains with
> 1245/255/63.
> Let me know...
This is because BIOS only provides info about how it sees the first two
drives (hda and hdb). For hdc and subsequent drives, with
;t support variable rate input, as far as I know. Could
that be the cause?
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
ime your
hibernate your notebook.
* The area may be password protected (within the drive), and you may need to
guess the password to get there.
Anyway, I believe that it'd be good to report the REAL geometry to the
user, but also the faked one so that he sees what's happening. Possibly
t's reported by the drive), you can get
Linux to see the extra space as a different device, but I don't believe
it is reasonable to have an extra API for this kind of accesses.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
o find it in the archives. Any help would be
> much appreciated - this upgrade has been hell.
Have you enabled VIA support in the kernel? Are you using the latest
kernel?
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
time) standard IDE
> devices no longer called chipset init. People either had no IDE, or
> were stuck in legacy mode. This fixes it.
>
> The IDE layer is in serious need of a cleanup though, IMHO...
Yes, yes, yes.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send th
whether it's the xor one or one the
other one) has thus invalid data.
Now how do you decide, after boot, which drive of the set, including the
xor drive is it the one that contains the invalid data? I think this is
not possible.
So you're out of luck at a trivial power failure w
On Thu, Oct 05, 2000 at 09:49:29AM +0200, Andi Kleen wrote:
> On Thu, Oct 05, 2000 at 09:39:34AM +0200, Vojtech Pavlik wrote:
> > Hmm, now that I think about it, this can be brought to data corruption
> > even easier ... Imagine a case where a stripe isn't written comple
Hi!
For those who like to try out the very latest developments, I'm
including my latest VIA and AMD IDE tuning drivers.
Just place all the files in drivers/ide of a 2.4 kernel and have fun.
Of course, I'm interested in all success/failure stories.
Thanks.
--
Vojtech Pavlik
ome interference inside the chip.
The time on the machine then behaves rather funny ... I wonder if this
affects other VIA chips as well or just my stepping CD silicon of the 686a.
By the way, any comments about the new VIA & AMD drivers, and the
ide-tuning.h include file?
--
Vojtech Pavlik
SuSE La
On Fri, Oct 06, 2000 at 08:04:42AM -0400, Byron Stanoszek wrote:
> On Fri, 6 Oct 2000, Vojtech Pavlik wrote:
>
> > Hi!
> >
> > For those who like to try out the very latest developments, I'm
> > including my latest VIA and AMD IDE tuning drivers.
> >
&g
> >Type: Plain Text (text/plain)
>
> What kind of game port do you have?
I think this bug is already fixed in the input CVS. I've sent a patch to
Linus now.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
IG_USB
>$CONFIG_INPUT
> dep_tristate ' USB HIDBP Mouse support' CONFIG_USB_MOUSE $CONFIG_USB
>$CONFIG_INPUT
>fi
Config.in is correct as is. hid.c vs usbkbd.c+usbmouse.c are two
different ways to drive the same devices (Full HID vs. HIDBP). You can't
use bot
ms as well. I've even seen systems shipped like that.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
m it will fail. Those are special case where an OEM has a
> drive maker adjust the skew tables to allow dirty tricks.
I'll have to try that.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Tue, Oct 10, 2000 at 11:17:31AM +0200, Markus Pfeiffer wrote:
> Vojtech Pavlik wrote:
> >
> > On Tue, Oct 10, 2000 at 12:43:33AM -0700, Andre Hedrick wrote:
> > Btw, reading the ATA/ATAPI-6 specs I think UDMA66 should work on a
> > setup where would be just one d
th this Andre's patch and your original setup
(the UDMA66 drive and the ZIP on one cable)? It'd answer a couple
questions.
--
Vojtech Pavlik
SuSE Labs
--- linux-2.4.0-t10-1-pristine/drivers/ide/ide-features.c Thu Aug 3 16:07:42
2000
+++ linux-2.4.0-t10-1.smsc/drivers/ide/ide-f
netic
> RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
> BuffType=unknown, BuffSize=256kB, MaxMultSect=0
> (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
> IORDY=yes, tPIO={min:180,w/IORDY:180}, tDMA={min:150,rec:150}
> PIO modes: pio0 pio1 pio2 pio3
> DMA modes:
On Tue, Oct 10, 2000 at 04:44:40PM +0530, [EMAIL PROTECTED] wrote:
> hi all,
> given struct netdevice for any pci network device, is there any way to get
> corresponding
> "struct pci_dev".
No.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the l
> hdb: set_drive_speed_status: error=0x04
> hdb: 244736kB, 239/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
> Partition check:
> hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 >
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
help.
Great. Thanks for your help, too.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
and three-connector cables 10<=l<=18.
ATA/ATAPI-6 draft rev. 0a, page 14 (sheet 28 of 404), table 2, row 4,
column 1, plus comment 4 in the same table.
And from the engineering point of view, it seems reasonable, too.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send
uot;40-wire assembly",
"80-wire assembly", both being three-connector cables with the
limitations you cite. Plus it talks about a "direct point-to-point
connection" for a single device case. There isn't any minimum length
specified for that case. This may be some relict in th
for
> single device being controlled by driver but i am not sure about multiple
> pci devices being controlled by same driver.
Yes, they do it, but they don't have to, they can point
pci_dev->driver_data to any structure they like. Expect this to happen
somewhere sometime.
-
On Tue, 10 Oct 2000, Vojtech Pavlik wrote:
> > > > Btw, reading the ATA/ATAPI-6 specs I think UDMA66 should work on a
> > > > setup where would be just one drive and a really short, 40-wire cable
> > > > without problems as well. I've even seen system
time of this kernel version, i'm not so sure if it's
> entirely a cvs problem since i've cvs'd bigger stuff than star-office and
> never got this error.
Note the "cvs server:" part. It's not you who is out of disk space, but
the OpenOffice CVS server.
--
ll be forwarding it to Linus, too, but I doubt it'll be accepted in the
current freeze of things, since it doesn't fix any critical bugs.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
sooner. The elevator will always be more
important to get right in terms of fairness to processes than bare
throughput.
> One catch, these tests require a native ATA-passthough
Do they? I believe I can do the same with a simple script ...
> and that will not be included until 2.5.
But yo
On Tue, Oct 17, 2000 at 01:15:26AM -0700, Andre Hedrick wrote:
> On Tue, 17 Oct 2000, Vojtech Pavlik wrote:
>
> > > Now we can profile drives to super-charge the elevator!!
> >
> > I doubt this will ever happen. We'll see IDE drives reorder the
> > re
ty.
But does this give any benchmarking benefit over traditional access via
/dev/hda?
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
ith ALI15X3 chipset.
>
> 4.- Would you recommend to put the old IDE drive as slave? does it slow
> down the access to the ATA66 one?
>
> Please, CC to my e-adress.
>
> cheers
>
> Francesc Oller
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
It can be replaced if you can desolder a 352 contact BGA chip. I don't
know of anyone who does.
Also, the vt82c686 will work just fine with Linux, but will be limited
to UDMA33, because UDMA66 on this chip does reliably fail.
Furthermore, these chips are very rare - I don't know anyon
gt; something cheap that locks them together. I will bring up ac-12 and check
> the error message...
Actually I'm beginning to suspect the PSU here ... does removing the
CD-ROM (leaving just the HDD and the ZIP in) help? Does the ZIP cause
errors even when connected just to the power cabl
t; I just acquired a new 1.1G athlon on an asus a7v133. It has a 686b.
> What should I expect w the 686b? and is the Via 686b data sheet
> available somewhere?
Make sure you use the latest 2.4.2-acxx drivers. Most other versions of
my drivers have little bugs in the 686b support. Harmless bu
t IDE interface.
If you wonder why /proc/ide/via reports slower DMA rates for the HDD
when the ZIP is connected is because the auto slowdown code kicks in and
lowers the transfer rate when too many CRC errors happen.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "
4.x series, so I added all the other changes to
the 3.20 driver, and 3.21 was born.
4.x is development
3.x is stable
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at h
On Thu, Mar 08, 2001 at 11:35:42AM -0700, Harold Oga wrote:
> On Thu, Mar 08, 2001 at 09:17:06AM +0100, Vojtech Pavlik wrote:
> >On Wed, Mar 07, 2001 at 01:23:49PM +, John Heil wrote:
> >Make sure you use the latest 2.4.2-acxx drivers. Most other versions of
> >my driver
he accuracy of the current algorithm
is +- .01 MHz.
Once tested a little more, the measurement will probably go in, however
with an option for the user to override it with a command line
parameter.
Btw, if it isn't a secret - what other drivers are those and what is the
exact method you used
tocol variations.
>
> Getting resync right is not as easy as detecting zero bytes. You
> should account for wild protocol variations in the world wide mouse
> population, too.
The new input psmouse driver can resync when bytes are lost and also
shouldn't lose any bytes if there are
On Wed, Mar 28, 2001 at 05:19:33PM -0600, [EMAIL PROTECTED] wrote:
> It's been rumoured that Vojtech Pavlik said:
> > On Wed, Mar 28, 2001 at 08:31:52PM +0200, Gunther Mayer wrote:
> > > [EMAIL PROTECTED] wrote:
> > > > It's been rumoured that Gunther Mayer
hwif->autodma = 1;
> +#endif /* CONFIG_IDEDMA_AUTO */
> }
> #endif /* CONFIG_BLK_DEV_IDEDMA */
> }
>
Linus, if you haven't applied my disable-dma-in-all-cases patch I've
sent you earlier, please do apply this one - it's correct and should be
th
hipset to 83 MHz FSB, you'll get 41.5 MHz
or 27.6 MHz PCI. And there are chips speced for 75 and 83 MHz FSB's -
Cyrix 6x86MX etc.
No way to get 33 here, if you *don't* want to over/under-clock the CPU.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line &q
o follow me :-(( ) just ask.
Yes. The IDE timing should be always the same, independent on the PCI
clock. However, it is programmed in terms of PCI cycles, so yes, the
only thing my driver does is exactly this compensation for the PCI speed
so that the IDE timing stays constant.
Yes, my driver is
$3000 machine sitting here that I can not do a damn thing with until I
> stop these blasted kernel deaths! (Yeah I'm pissed, but at the situation
> not at the kernel or anyone involved with the VIA stuff. Please don't take
> it that way.)
Sure, I'll need a more precise
On Mon, Jan 29, 2001 at 12:49:16PM -0800, Tim Moore wrote:
> Is via82cxxx.c v3.17 a 2.4.x only patch or did I miss something else?
Yes, it's currently 2.4.x only.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bo
On Tue, Jan 30, 2001 at 10:48:26AM +0100, Vojtech Pavlik wrote:
> The current VIA driver in 2.4.0 is version 2.1e. I wouldn't push a new
> version, but VIA has released the vt82c686b chip and it's causing a lot
> of trouble.
>
> The 2.1e version can't recognize i
27;ll help a lot of people and I'll be getting much less
mails about non-working 686b's.
It's against 2.4.1-pre12, but should patch cleanly against pre11 or
anything later.
Thanks.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe lin
he Advansys SCSI and a Tulip
NIC drivers? It isn't related anyhow.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Tue, Jan 30, 2001 at 11:55:25PM -0800, David Raufeisen wrote:
> On Wednesday, 31 January 2001, at 08:36:42 (+0100),
> Vojtech Pavlik wrote:
>
> > Hi!
> >
> > 1) You don't seem to have any drives on the VIA controller. If this is
> > true, I don't
er
> responsiveness than 2.4.x . Could this be because of via problems on
> the 2.4.x kernel or is it 2.4.x arch ?
No, probably not.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
lems i've been talking about
Btw, if you run your FSB at 114 MHz, you need to pass 'idebus=38' to the
IDE driver so that it knows your PCI bus runs at 38 MHz (3x38 = 114).
Otherwise you'll get incorrect timing etc.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list
/dev/hd*, hdparm -i /dev/hd*, cat /proc/ide/via) data for both
so that I can compare them?
If I find any differences, I'll know what the bug is.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
n ide-reset error
> on bootup because the instructions are too fast. The VIA driver on 2.2 doesn't
> correctly program the PCI card, so you don't see weird behavior running 2.2
> with a faster PCI clock.
>
> (Note: 1.14 * 33 = 37.6 PCI Clk)
It's 38:
114 / 3 == 38 == 1.1
1 | 15 | 4T=33.3 2T=66.6
686b |33 |1 2 1 | 10 | 6T=33.3 4T=66.6 2T=100.0
... that is, if the 686b indeed has a 100MHz clock source. If not, then
in the case of 25 MHz, T would be 13.3ns. If you can verify this, it'd
be nice.
--
Vojtech Pavlik
Su
should use the correct idebus= so that the Active/Recover
timings are correct. If KT7A doesn't work with UDMA at high PCI clocks
*even when* idebus= is correct would mean that the UDMA timing is in
1/(PCICLK*3) units instead of units of 10ns.
Anyone help us?
--
Vojtech Pavlik
SuSE Labs
-
ong timeout = jiffies + ((HZ + 19)/20) + 1;
> > > while (0 < (signed long)(timeout - jiffies));
> >
> > On that bit we agree.
>
> What do you want fixed?
> Send a patch and lets try it
How about this?
--
Vojtech Pavlik
SuSE Labs
--- pdc202xx.c.old Fri Jul 2
e major release
numbers to 4 and 2.
Could anyone with these chipsets check these drivers if they detect the
PCI clock correctly on their systems?
Thanks.
Just untar the attached file into drivers/ide and recompile.
--
Vojtech Pavlik
SuSE Labs
amd-2.0+via-4.0.tar.bz2
rrect detected PCI clock, and not just VIA/AMD's.
Unfortunately the PCI speed measuring code needs help from the chipset
itself, so it isn't possible to implement in generic code. Maybe a
callback could be added to the chipset-specific drivers, though ...
I do have some plans with ide-pci.c, so ...
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
needed. However, it still might be
worth to pass the PCI speed to other drivers ...
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
h'?)
> Any idea?
Since version 2.30 of the VIA driver (2.4.2-pre2), the driver leaves
prefetch as is set by BIOS. It seems that ATAPI devices need this set to
off at least on some of the VIA chips.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe
c drivers. Other non IDE devices, such as matroxfb,
> > may be interested in PCI speed too.
>
> that file will most likely go away in 2.5
Good, it should.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
t; the driver back to a hardcoded 33.
>
> What should I do next?
Are you willing to do some experiments? I suppose the 686b is somewhat
different than the other chips (I tested it on 686a and 586b).
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscri
t; atkbd driver, you have to turn off hardware auto repeat for this to
> take effect.
By sending the events, the driver is asked to change the delay/repeat
rate. It should work in the software autorepeat and in the hardware
autorepeat cases.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
not set
> # CONFIG_NLS_ISO8859_8 is not set
> # CONFIG_NLS_CODEPAGE_1251 is not set
> CONFIG_NLS_ISO8859_1=m
> # CONFIG_NLS_ISO8859_2 is not set
> # CONFIG_NLS_ISO8859_3 is not set
> # CONFIG_NLS_ISO8859_4 is not set
> # CONFIG_NLS_ISO8859_5 is not set
> # CONFIG_NLS_ISO8
>
> That's what we like Linux for. It doesn't get confused when everything
> else does :-)
>
> Thanks for your very interesting reply.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
0bb Before first symbol
> Code; 0010 Before first symbol
> 10: 31 c9 xor%ecx,%ecx
> Code; 0012 Before first symbol
> 12: 8d 70 00 lea0x0(%eax),%esi
>
> The module loaded OK in 2.4.5-ac3. input, joydev, ns558, gamepor
On Thu, May 31, 2001 at 11:29:06AM +1000, Keith Owens wrote:
> On Wed, 30 May 2001 18:15:31 +0200,
> Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> >On Wed, May 30, 2001 at 02:46:42PM +1000, Keith Owens wrote:
> >> This is messy. gameport.h is included by code outside
On Thu, May 31, 2001 at 05:52:39PM +1000, Keith Owens wrote:
> On Thu, 31 May 2001 08:08:45 +0200,
> Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> >On Thu, May 31, 2001 at 11:29:06AM +1000, Keith Owens wrote:
> >> With your patch, if a user selects
On Thu, May 31, 2001 at 10:06:54AM +0200, Vojtech Pavlik wrote:
> On Thu, May 31, 2001 at 05:52:39PM +1000, Keith Owens wrote:
>
> > On Thu, 31 May 2001 08:08:45 +0200,
> > Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> > >On Thu, May 31, 2001 at 11:29:06AM +100
am reporting
> it to you.
>
> I and another user thought the problem was in hid_input_field, but upon
> looking I now think not.
>
> My mouse is fairly unusable in X, and unfortunately I can not figure out
> a fix.
It is a quite stupid bug. Here is the fix (already sent to Al
On Fri, Jun 01, 2001 at 10:57:17AM +0100, Michael wrote:
> On Wed, May 30, 2001 at 09:30:39PM +0100, Alan Cox wrote:
> > 2.4.5-ac4
> > o Update USB hid drivers (Vojtech Pavlik)
>
> I think these changes have broken my USB wheel mouse.
>
>
as been loathed by some. In 322 lines of code, all of
serial mouse handling. And much better than ever before.
Try it out. Installation notes are in the README file.
Patch against 2.4.5-ac9.
Have fun ...
--
Vojtech Pavlik
SuSE Labs
sermouse.tar.gz
eers: dumb serial
> port, serial mouse, joystick, etc.
Agreed. Completely.
And proposed a couple times before.
But not in my power.
So I used a N_MOUSE line discipline instead
- the best tap into the serial/tty stack I found.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from thi
e it indeed is.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
eeded for serial devices as well as video terminals.
> Your work might help speed up devleopement.
Sounds cute. Where do I find the result of your work?
> > NB, Ted Tytso mentioned something at the 2.5 conference about integrating
> > some of the serial layer with the tty layer
rence - on USB you always get whole packets,
while over serial port the data is processed byte by byte and thus we
know a little of the information before the whole packet arrives.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
th
faster than
exponentially (base 2). I haven't been able to stop that fast.
> > > [If so, what kind of update rate would it do on USB?]
> >
> > It wouldn't make any difference - on USB you always get whole packets,
> > while over serial port the data is processed
On Fri, Jun 08, 2001 at 03:19:46PM -0500, Mike Coleman wrote:
> Vojtech Pavlik <[EMAIL PROTECTED]> writes:
> > > Can't it make mouse jump forward and back when user suddenly stops?
> >
> > In theory - yes. It doesn't seem to be a problem in practice, th
, 0x10, 0x2f, VIA_UDMA_66 },
> { "vt82c686", PCI_DEVICE_ID_VIA_82C686, 0x00, 0x0f, VIA_UDMA_33 |
>VIA_BAD_CLK66 },
> { "vt82c596b", PCI_DEVICE_ID_VIA_82C596, 0x10, 0x2f, VIA_UDMA_66 },
Not sure what version you're using, but if it's 3.23 (I b
rything is OK, add your
Signed-off-by: line?
> Signed-off-by: Peter Osterlund <[EMAIL PROTECTED]>
> ---
>
> Documentation/input/appletouch.txt | 120 +
> drivers/usb/input/Kconfig | 19 +
> drivers/usb/input/Makefile |1
> drivers/usb/input/appletouch.c |
future, we could add here code to search for
> + * a second finger...
> + * for now, scrolling using the synaptics X driver is
> + * much more simpler to achieve.
> + */
This could be quite useful, too,
. Should I wait for that or apply the patch you just sent?
> > This could be quite useful, too, for right and middle button taps (2 and
> > 3 fingers) - since the Macs lack these buttons.
>
> Indeed. But this can be a later improvement, let's make one finger work
> for no
519 2299 0.99314 -0.7
864 1381 1.01829 1.8
--
Vojtech Pavlik
SuSE Labs, SuSE CR
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vge
On Tue, Jul 12, 2005 at 10:39:00PM +1000, Con Kolivas wrote:
> On Tue, 12 Jul 2005 22:10, Vojtech Pavlik wrote:
> > The PIT crystal runs at 14.3181818 MHz (CGA dotclock, found on ISA, ...)
> > and is divided by 12 to get PIT tick rate
> >
> > 14.3181818 MHz /
e the 0.0 case, and 18Hz is not bad either. IIRC, DOS used 18HZ ;)
> http://jengelh.hopto.org/tick/
DOS used 65535 as the divisor (ticks/jiffie), which doesn't give an
integer HZ.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
-
To unsubscribe from this list: send the line "unsubscribe li
> the range of 848ppm for HZ=1000 BECAUSE we need to follow the
> standard. You can easily see this with the current 2.6 kernel. We
> even have a bug report on it:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=3289
Going to HZ=864 would fix this problem. It would likely cause other
gt; > Actually we have this in input tree:
> > >
> > > static inline void
> > > usb_to_input_id(const struct usb_device *dev, struct input_id *id)
> >
> > This cleans up a lot of code indeed. Too bad this is not upstream yet...
> >
>
> It is in
; Hi,
>
> Could you please provide us with debug dmesg - just boot with
> i8042.debug on kernel command line.
Also try the usual options ("i8042.nomux=1" and "usb-handoff"). One or
both may make the problem disappear.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
-
To unsu
consider the RTC again.
Another BIG problem with RTC is that it doesn't allow reading its
internal counter like the PIT does, making TSC interpolation even harder.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&q
critical (remembering that the
> kernel doesn't do floating point math)
No, but 1/1000Hz = 100ns, while 1/864Hz = 1157407.407ns. If you have
a counter that counts the ticks in nanoseconds (xtime ...), the first
will be exact, the second will be accumulating an error.
It's a tra
ters a whole lot
> less.
A note on the relaive timer API: There needs to be a way to say
"x milliseconds from the time this timer should have triggered" instead
of "x milliseconds from now", to avoid skew in timers that try to be
strictly periodic.
But other than that - such an
101 - 200 of 554 matches
Mail list logo
