assumes 1:1 mapping between Linux keycodes
and what the keyboard sends, which I can't believe is the case.
--
Vojtech Pavlik
Director SuSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
GA code changes with different keyboards attached?
> Best regards,
>
> Javier
>
> Vojtech Pavlik escribió:
>> On Thu, Jan 31, 2008 at 01:18:22AM +0800, Bryan Wu wrote:
>>
>>> +static irqreturn_t opencores_kbd_isr(int irq, void *dev_id)
>>> +{
>>&g
much more complicated, and it gives you all
these benefits even with secure boot disabled.
--
Vojtech Pavlik
Director SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
rcise is to minimize the number of writes to
> the NVRAM. The hash changes with every hibernation, obviously.
The key should, too.
--
Vojtech Pavlik
Director SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@v
than the next kernel can do the
> > validation since the validating key has to be secret
>
> This is true, but as you said, the relevance of this seems to be rather
> questionable.
Indeed, it's hard to imagine a scenario that is also valid within the
secure boot threat mod
d Mr Evil Blackhat would have
> to find a new bunch of identity documents to create a new account to
> repeat the process.
Yes, from the point it gets blacklisted, it's fairly clear. You're
forced to reboot, but under the Secure Boot model, you have to do that
on any system that used cod
s is
> the wrong place
> to ask. If there are better places to be looking for this data I am
> happy to RTFM there.
>
> Now trying 2.4.3-ac6 to see what happens there.
idebus= isn't used in case there is no VL-BUS or PCI bus in your system.
--
Vojtech Pavlik
SuSE Labs
-
To unsu
data and assume the cable is present, use 'ide0=ata66' or
> * 'ide1=ata66' on the kernel command line.
> *
>
> I've tried with ide0=ata100, but this options doesn't work.
Try ide0=ata66 instead. The option should have been named ide0=80wire,
but, well, &q
On Thu, Apr 19, 2001 at 04:46:03PM +0200, David Balazic wrote:
> Vojtech Pavlik ([EMAIL PROTECTED]) wrote :
>
> > On Wed, Apr 18, 2001 at 10:21:53PM -0400, Manuel Ignacio Monge Garcia wrote:
> >
> > > El Mié 18 Abr 2001 15:16, escribiste:
> > > > I d
Hi Andre!
You wanted my VIA driver for 2.2. Here is a patch that brings the very
latest 4.2 driver to the 2.2 kernel. The patch is against the
2.2.19-pre13 kernel plus yours 1221 ide patch.
Enjoy!
--
Vojtech Pavlik
SuSE Labs
via-4.2x-for-2.2.19-pre13-ide1221.diff.bz2
ier test already only
loosening it. Because of that, it's superfluous. And the code relies on
the compiler to optimize it out.
If written like:
#ifndef CONFIG_IDEDMA_IVB
#define IDE_UDMA_MASK 0x4000
#else
#define IDE_UDMA_MASK 0x6000
#endif /* CONFIG_IDEDMA_IVB */
byte eighty_ninty_three (id
..)? What are the drives (hdparm -i ...)?
I can send you the VIA latest drivers if you are interested in trying
whether they'll help.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Mo
able DMA instead.
Hmm, I'll have to look into this anyway - many users seem to do that and
it isn't as harmless as it looks (it worked by pure luck with the
previous version).
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Tue, Feb 20, 2001 at 11:15:02PM -0800, Shane Wegner wrote:
> On Wed, Feb 21, 2001 at 08:09:19AM +0100, Vojtech Pavlik wrote:
> > On Tue, Feb 20, 2001 at 03:59:27PM -0800, Shane Wegner wrote:
> >
> > > > You wanted my VIA driver for 2.2. Here is a patch that brings
On Wed, Feb 21, 2001 at 11:05:33AM -0300, Rogerio Brito wrote:
> On Feb 21 2001, Vojtech Pavlik wrote:
> > On Tue, Feb 20, 2001 at 11:15:02PM -0800, Shane Wegner wrote:
> > > Ok, can I still use -u1 -k1 -c1 on the drives or is it even
> > > necessary anymore.
> >
-d1 -X69 /dev/hda => I get 36MB/s
>
> Then I tried kernel 2.4.1. I issued exactly the same hdparm command.
> i got in syslog the message: "ide0: Speed warnings UDMA 3/4/5 is not
> functional"!
>
> What is the problem?
The 80-wire cable was not detected. Try this driver
r unrecommended to set it with hdparm?
It does:
via82cxxx.c, line 536: hwif->drives[i].io_32bit = 1;
Actually this seems to be required for correct operation in PIO modes.
Anyway, it doesn't have an effect if DMA/UDMA modes are used -
BusMastering is always 32bit.
--
Vojtech Pavlik
SuS
dev/hda
> keepsettings = 0 (off)
>
> Is this normal?
This only relates to a ide bus reset in case of a failure, not system reset.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTE
exactly 18",
not longer, not shorter.
--
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/
oard, and disabled everything but USB.
No, they have a separate USB chip, but it has the same PCI ID as the
builtin silicon in the southbridge.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTE
On Mon, Mar 05, 2001 at 04:37:00PM -0500, David Riley wrote:
> Alan Cox wrote:
> > 2.4.2-ac12
> > o Update VIA IDE driver to 3.21 (Vojtech Pavlik)
> > |No UDMA66 on 82c686
>
> Um... Does that include 686a? 82c686a is supposed to ha
ip? This change was brought in because I wasn't sure for the 10 and 11
revisions. 586a doesn't have a functional UDMA66 engine and causes
crashes if programmed to UDMA66.
> 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South] (rev 11)
It's the revision number -
On Tue, Mar 06, 2001 at 10:29:00AM +0100, Mike Galbraith wrote:
> On Tue, 6 Mar 2001, Vojtech Pavlik wrote:
>
> > On Tue, Mar 06, 2001 at 10:09:05AM +0100, Mike Galbraith wrote:
> >
> > > The driver forget what it always called a vt82c596b before. Reverting
> &g
-
Vojtech Pavlik
SuSE Labs
#ifndef _IDE_TIMING_H
#define _IDE_TIMING_H
/*
* $Id: ide-timing.h,v 1.4 2000/10/02 20:48:56 vojtech Exp $
*
* Copyright (c) 1999-2000 Vojtech Pavlik
*
* Sponsored by SuSE
*/
/*
* This program is free software; you can redistribute it and/or modify
* it under th
station
> Working: Microsoft Windows 98 First Edition on the Via.
What modules are loaded?
What's in /proc/bus/usb/devices?
What's in dmesg?
--
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/
omplaining type. no idea which
> applies there, either.
>
> --
> dep
> --
> bipartisanship: an illogical construct not unlike the idea that
> if half the people like red and half the people like blue, the
> country's favorite color is purple.
> -
> To unsubscribe fro
t; archives or documentation, Can this cause file system corruption in any way?
>
> abosolutely not. udma checksums each transfer. when checksums don't match,
> the *hardware* retries the transfer (and incidentally reports the event,
> which Linux obligingly passes on to you.)
The
> <4>hdb: TF.1=x00 TF.2=x00 TF.3=x00 TF.4=x00 TF.5=x00 TF.6=x40 TF.7=xf8
> <6>hdb: QUANTUM FIREBALL CR4.3A, 4110MB w/418kB Cache, CHS=14848/9/63, UDMA(66)
> <4>hdc: ATAPI 50X CD-ROM drive, 128kB Cache, UDMA(33)
> <6>Uniform CD-ROM driver Revision: 3.11
> <4&g
got a vt82c586 here (bought it just for testing of this problem),
and I wasn't able to create any corruption using that board and the 2.4
drivers.
Does anyone still have any vt82c586 or vt82c586a the 2.4 VIA driver is
corrupting data on?
I'd like to hear about such reports so that I c
What's in /proc/ide/via?
3) What says hdparm -i on your devices?
4) If you mount your filesystem read-only, does it read garbage?
Thanks.
--
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/
a hdparm to enable DMA and poo
> lost all data reinstall necessary from scratch
Is this problem still present with 2.4.0? Well, you don't need to kill
your data to test this - make sure the kernel is mounting the
filesystems read only in the test. DMA will be probably enabl
- Alan's IDE patch for 2.2 kills autodma on ALL VIA chipsets.
That's because all VIA chipsets starting from vt82c586 to vt82c686b
(UDMA100), share the same PCI ID.
Would you prefer to filter just vt82c586 and vt82c586a as the comment in
Alan's code says or simply unconditionally
0)
> | Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
>SERR- FastB2B-
> | Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- | 00: 06 11 40 30 00 00 80 02 10 00 80 06 00 00 00 00
> | 10: 00 00 00 00 00 00 00 00 00 00 00 00 0
]>
> > > To: Linus Torvalds <[EMAIL PROTECTED]>
> > > Cc: Vojtech Pavlik <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> > > Subject: Re: ide.2.4.1-p3.01112001.patch
> > >
> > > > what the bug is, and whether there is some other work-around, an
s Alan's code does?
>
> I'd take a 2.2 patch to cut down the range too
I can make one for you, but first I'd like to find out what exactly are
the problem cases.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
other chips.
Btw, this is not the 586 nor 586a, so changing the test to test for just
these two probably won't be the right thing to do ...
--
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/
ly all these chips use PIIX-compatible extensions to the PCI
bus, so they are all interchangeable to some degree.
> I'm curious if all of the other boards in Alans bug reports also
> fall into the stranger category.
It's possible. I have a board (VA-503A), which has a masqueraded
On Fri, Jan 12, 2001 at 04:09:22PM -0800, Linus Torvalds wrote:
> On Fri, 12 Jan 2001, Vojtech Pavlik wrote:
> >
> > However - Alan's IDE patch for 2.2 kills autodma on ALL VIA chipsets.
> > That's because all VIA chipsets starting from vt82c586 to vt82c686b
>
dparm -d1 or hdparm -X66 or similar
stuff in your init scripts.
> I will
> also try your 3.11 driver, which seems to be an enormous cleanup.
the 2.1e driver is an enormous cleanup of the original driver from the
2.2 kernels. the 3.11 is an enormous cleanup of 2.1e, yes.
> Btw, do
> y
he VIA
driver, please speak up, so I can fix it.
I'm not currently looking for success reports, I've already got success
reports for every type VIA IDE chip out there.
I'll need the motherboard type and revision, lspci -vvxxx, dmesg,
hdparm -i and /proc/ide/via listings ...
Thanks.
Hi!
This is not the case I'm looking for. You have a 686b, a chip that is
not supported in 2.4.0 yet. You can try the via 3.11 driver I posted a
while ago, it adds support for this chip, including UDMA100.
Thanks anyway,
Vojtech
On Sat, Jan 13, 2001 at 09:09:05AM -0800, Bryan O'
controller thus can read everything OK. When writing, the
controller provides the clock and for some reason the Samsung can't keep
up with the setting the driver selects for it. The question is why and
why the driver selects the incorrect (or just too tight?) value.
--
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/
A-503A), which has a masqueraded 598,
> > which identifies itself as 597, and a 686a southbridge. This got the
> > 2.2 ide driver completely confused, for example.
>
> Maybe the VIA IDE chipset support option should depend on PCI quirks now ?
No, in 2.4 the VIA IDE driver doesn&#
ied, I'll probably submit another
one that will allow to override the no-dma rule by a kernel command line
option, as Alan Cox suggested.
--
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 Sun, Jan 14, 2001 at 09:45:09AM +0100, Tobias Ringstrom wrote:
> On Sun, 14 Jan 2001, Vojtech Pavlik wrote:
> > On Sat, Jan 13, 2001 at 11:36:13PM +0100, Tobias Ringstrom wrote:
> >
> > > I have now tried the SAMSUNG VG34323A disk with two other controllers at
> >
means a single CRC error
which is recovered from correctly, then that actually means 'working and
probably would work perfect with a shorter cable'.
--
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/
quot;.
>
> Note that "hdparm -X34 -d1" enables old DMA, not UDMA. (The board was
> advertised as UDMA capable but it isn't AFAIK).
It should be able to do UDMA33.
Is the board still available for some testing?
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from thi
17, 2001 at 02:38:00PM -, Chandler, Alan wrote:
> On Wed Jan 10 2001 - 06:45:24 EST Vojtech Pavlik <[EMAIL PROTECTED]> wrote
>
> >For all of you who had problems getting the VIA IDE driver to work
> >correctly on the 686b, here is a driver that should work with those
bit memory at 0xea02 [0xea02].
> > Bus 0, device 10, function 0:
> > Ethernet controller: 3Com 3C905B 100bTX (rev 36).
> > Medium devsel. IRQ 11. Master Capable. Latency=64. Min
> > Gnt=10.Max Lat=10.
> > I/O at 0xe000 [0xe001].
> >
then you can read it back and checksum the contents.
>
> It does destroy the content on the drive, this is no worse than a random
> "File System Corruption " because it absolutely destroys or corrupts the
> original content for testing purposes.
>
>
> On Wed, 17 J
On Wed, Jan 17, 2001 at 11:53:36AM -0700, Terrence Martin wrote:
> Vojtech Pavlik wrote:
>
> > Hi!
> >
> > Ok, just for a test, before I finish the 2.2 version of the new VIA IDE
> > driver, could you try with the 2.4.0 kernel if it fixes the behavior?
> >
>
-test6, IIRC, and 2.4.1-pre7). I find it odd
> that if it isn't a kernel-related problem, that it's only manifesting itself
> under 2.4.
>
> I'm running a slot A athlon on an abit KA7-100.
My bet is ACPI/powermanagement messing with it ...
--
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/
ittle more foolproof with respect to the 'idebus'
setting, which is quite a misnomer, btw.
Care to try them out?
Andre, you're the only one I know of having the 766 chip, so please test
this driver, I'd like to know if it really works ... thanks.
--
Vojtech Pavlik
SuSE Labs
via-amd-ide.tar.bz2
r.bz2 attachment to
> Vojtech Pavlik's mail which were placed in drivers/ide directory -
> ERRORS.
> Alan
Wonderful! A case where I can compare a working setup with a nonworking
one! :) Could you please send me the usual stuff (dmesg, lspci -vvxxx,
cat /proc/ide/via, hdparm -i
make that VIA UDMA66 ide working correctly when they have a
UDMA100 HPT370 onboard)?
... btw, if we ever implement UDMA slowdown code based on CRC errors, we
should differentiate between CRC errors on read and CRC errors on write,
because each are caused by a different problem ...
--
Vojtech Pa
remembering, no disrespect is intended.)
Me, most likely.
> Is anyone out there with as close a match to my setup as possible wish to
> help me with this? (I'm not discounting the mismatched setups, I just want
> a baseline to go from. If someone with my setup is NOT ahving trouble then
> I may need to look at something different).
--
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/
ed (note, only tested ext2
> fs). I did disable UDMA everywhere and still saw it happen, this problem is
> not present in older 2.4.0-test kernels so it's something in the late
> pre-release stage and into the release stage.
Do you have the via driver compiled in? If yes, try without
gt; CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=16514064
> tDMA={min:120,rec:120}, DMA modes: sword0 sword1 sword2 mword0 mword1
> mword2
> IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
> UDMA modes: mode0 mode1 *mode2
>
> --
>
> /dev/hda:
> T
On Sun, Jan 21, 2001 at 01:42:41PM +0100, Mike Galbraith wrote:
> On Sun, 21 Jan 2001, Vojtech Pavlik wrote:
>
> > On Sat, Jan 20, 2001 at 02:57:07PM -0800, Andre Hedrick wrote:
> >
> > > chipset ---\
> > > |
> > >
proc/ide/via
I'll see what I can do about the driver.
--
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/
he clock
went weird with a 10 ms accuracy. And compensate for that. It should be
possible to keep a 'reasonable' clock running even through the clock
changes, where reasonable means constantly growing and as close to real
time as 10 ms difference max.
Yes, this is not perfect, but still
86" and "586/non-AMD 5x86/6x86/6x86MX"...?)
If I recall correctly:
Am5x86 == AMD X5 == a very fast 486 processor with a big WB cache
Cx5x86 == IBM 5x86 == a slow Pentium-like processor in a 486 socket
So yes, for the AMD 5x86 you have to select '486'.
--
Vojtech
input/joydev.c:
Fix possible overflows in connect and open. [critical]
drivers/input/mousedev.c:
Fix possible overflows in connect and open. [critical]
Add missing randomness reporting.
Please apply it.
Thanks.
--
Vojtech Pavlik
SuSE Labs
diff -urN linux-2.4.0-test11-pre6/dr
CPU speed (or STPCLK ratio).
> BTW I mailed patch to do exactly that kind of autodetection to the
> list some time ago. (I just can't find it now :-( -- search archives
> for 'TSC is slower than it should be'.
If I recall correctly, that patch didn't create a 'reas
ans you can no longer detect speed change after 10msec:
> >
> > going from 150MHz to 300MHz is very similar to one lost timer
> > interrupt.
> >
>
> That's the point.
... and, you still can have both - detection of lost timer interrupts
and detection of speed cha
. There are ISA-sytle NE2000's on PCMCIA, but
1) You know that you have a card there via the PCMCIA services and
2) They're not the old crappy NE2000's that'd die on a random read anyway.
--
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/
en for those ... I think EHCI
should handle even 1.x devices ... I may be wrong, though.
--
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/
change anything else.
It's against 2.4.0-test11.
--
Vojtech Pavlik
SuSE Labs
diff -urN linux-2.4.0-test11/drivers/net/pcnet32.c linux/drivers/net/pcnet32.c
--- linux-2.4.0-test11/drivers/net/pcnet32.cTue Nov 21 23:04:24 2000
+++ linux/drivers/net/pcnet32.c Tue Nov 21 20:56:57 2000
@@ -
. but is there a reason why for example AMD 486's couldn't work in a
82489DX-based SMP board?
--
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/
are put into the .data segment, which
*is* in the object file.
Thus a difference of 12 bytes code size in your case (on a 32 bit system).
--
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/
5456
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>5Mbs RotSpdTol>.5% }
> RawCHS=1011/15/22, TrkSize=11264, SectSize=512, ECCbytes=4
> BuffType=3(DualPortCache), BuffSize=32kB, MaxMultSect=8, MultSect=off
> DblWordIO=no, OldPIO=2, DMA=no
> CurCHS=1011/15/22, CurSects=
le to NULL, it's because my code actually relies on
> it; I don't want that information eliminated.
Yes, but if it generates a bigger (== worse) binary?
--
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/
"just" a few bytes in every driver, in a
way that is safe and simple (and commenting out the = 0 is a safe way),
you get a lot of space saved in the sum.
--
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/
dered a bug and is the
> volatile declaration its fix?
Yes. The compiler was optimizing too much.
> If so, is there any way to have /dev/tty1 on a no graphic card i386 machine?
> (besides unvolatilizating *p wich works for me)
I think you can use serial console instead, if you have seri
ASUS-CUSL2 has
>
> or the
>
> (2) Intel I/O Controller Hub 2 (ICH2)
>
> I'd like to get my system working using the built-in ATA100 controller
> on the ASUS CUSL2, but what options do I need in 2.4.0-test11's kernel
> config ?
>
> Is there support for the
with mgaHALlib.a ...
The Matrox driver referenced above uses this lib.
--
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/
he
driver, and I'll send a patch to Linus soon, along with a couple more
enhancements to the driver (better via82c596b detection).
--
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 is as problemless as
version 2.1, I'll send this to Linus for inclusion in the kernel.
--
Vojtech Pavlik
SuSE Labs
--- via82cxxx.c-2.1 Tue Aug 29 11:19:27 2000
+++ via82cxxx.c Tue Sep 12 13:02:22 2000
@@ -1,5 +1,5 @@
/*
- * $Id: via82cxxx.c,v 2.1 2000/08/29 01:34:60 vojtech Exp $
+ * $Id
kes it
> crash.
>
> If necessary I can again provide the boot log and a verbose lspci and whatever
> else is desired. I'll even let you log in and look at it.
I can look into this. I don't guarantee I'll find the problem, but I've
got all the PIIX datasheets handy now
yes, for 2.4.0 the latest pppd is needed,
older pppd's causing the above described error.
--
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 Thu, Sep 14, 2000 at 01:36:39AM +0200, Bartlomiej Zolnierkiewicz wrote:
> On Tue, 12 Sep 2000, Vojtech Pavlik wrote:
>
> > Anyone interested, please test this out, if it is as problemless as
> > version 2.1, I'll send this to Linus for inclusion in the kernel.
>
ut and the fixes for
> Cobra 7403 need to be added to make it a generic amd74xx.c
>
> Cheers,
>
> On Thu, 14 Sep 2000, Vojtech Pavlik wrote:
>
> > On Thu, Sep 14, 2000 at 01:36:39AM +0200, Bartlomiej Zolnierkiewicz wrote:
> >
> > > On Tue, 12 Sep 2000,
also.
The same happens for OHCI on new Macs. The correct function to use is:
pci_enable_device(dev);
This function will enable the i/o, mem and irqs, and assign them if they
were not assigned for some reason, too.
And you should use it on any PCI device you want to use before using
it, on all
Hi!
For those who are interested in testing my VIA IDE code, here is another
release that configures the thing even better. IDE timing is black
magic. ;) It's a drop-in replacement for the 2.1 driver.
I'm interested in failure/success reports.
Thanks.
--
Vojtech Pavlik
SuSE Labs
Hi!
While developing the next versions, I found two 'obvious bugs' in the
2.1 version. They are not very harmful. The attached patch fixes them.
--
Vojtech Pavlik
SuSE Labs
--- linux/drivers/ide/via82cxxx.c.old Mon Sep 18 22:10:10 2000
+++ linux/drivers/ide/via82cxxx.c Mon
Conf/Chan. : 08 08
> > Threshold Prim. : 1/2 1/2
> > Read DMA FIFO flush: on on
> > End Sect. FIFO flush: on on
> > Max DRDY Pulse Width: No limitation
> > Bytes Per Sector
into test9-pre6, because otherwise it's quite
unusable for vt82c596a users.
TIA.
--
Vojtech Pavlik
SuSE Labs
--- linux-old/drivers/ide/via82cxxx.c Wed Sep 6 17:07:56 2000
+++ linux/drivers/ide/via82cxxx.c Wed Sep 20 23:33:08 2000
@@ -1,5 +1,5 @@
/*
- * $Id: via82cxxx.c,v 2.1 2
case BTN_SIDE: if (list->mode > 1)
>index = 3; break;
> case BTN_2:
> case BTN_STYLUS2:
> case BTN_MIDDL
s that need to
be possible to load/unload separately.
--
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/
ering).
Just do it the way most other subsystems do it - have a
drm_[un]register_driver() functions, which are exported by the DRM
generic module and have the card-specific modules call that. This way
the DRM generic module will know what drivers are loaded.
For an example see the PCI subsystem,
is all has been discussed many many times around with little
benefit.
--
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 exists in more chips as well.
If anyone owning a motherboard with the vt82c686a chip (VIA with UDMA66
and audio), could test this, I'd appreciate that.
Attached is a patch that makes the problems go away by reprogramming the
chip in the problematic case.
--
Vojtech Pavlik
SuSE Labs
diff -
> > If anyone owning a motherboard with the vt82c686a chip (VIA with UDMA66
> > and audio), could test this, I'd appreciate that.
>
> I've this kind of motherboard without audio.
Well, the audio function is integrated in the chip, possibly just disabled.
> > A
A PCI to ISA Bridge
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>Stepping+ SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 0
Oh, this is a newer revision than mine (silicon CF or CG) - I
#x27;.
It fixes the blanking, but squid, wmclock (and other apps using
gettimeofday()) will still cause trouble.
--
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/
ill X then to reboot.
>
> Anyway, thanks for your explaination...
> I'll do a feedback for this patch ASAP.
Interesting. If it's caused by SCSI as well (might be), then it's not
caused by heavy IDE activity but rather than that it could be heavy
BusMastering activity instead
;s time to hunt for
i8259 accesses in the kernel that lack the necessary spinlock, even when
they're not probably the cause of the problem we see here.
--
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/
wrong moment), they're possible.
However, these don't seem to be the cause of the problem we see here
anyway.
--
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/
so it isn't an IDE problem.
Uh, guess too many negations. You wanted to say that the problem was
present even when you disabled the IDE subsystem, right?
So now it seems that possibly enough PCI traffic / busmastering traffic
can cause the problem ...
--
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/
be nice to verify that the problem also happens when the system
is not running out of memory (which -j10 quite causes I think) ...
--
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/
1 - 100 of 554 matches
Mail list logo
