This enum leaks out to userspace via error messages, so fix the spelling.
Signed-off-by: Bill Nottingham
---
drivers/misc/mei/hbm.c | 8
drivers/misc/mei/hw-me.c | 2 +-
drivers/misc/mei/init.c| 4 ++--
drivers/misc/mei/mei_dev.h | 2 +-
4 files changed, 8 insertions(+), 8
This enum leaks out to userspace via error messages, so fix the spelling.
Signed-off-by: Bill Nottingham nott...@redhat.com
---
drivers/misc/mei/hbm.c | 8
drivers/misc/mei/hw-me.c | 2 +-
drivers/misc/mei/init.c| 4 ++--
drivers/misc/mei/mei_dev.h | 2 +-
4 files changed, 8
Jan Engelhardt ([EMAIL PROTECTED]) said:
>
> Make the vt return to the system default when it is reset.
> Also make UTF-8 the system default.
> Derived from http://lkml.org/lkml/2007/8/31/246
>
> Tested and works as expected.
Fine with me. I believe the original patch I sent went to -mm, so
Jan Engelhardt ([EMAIL PROTECTED]) said:
Make the vt return to the system default when it is reset.
Also make UTF-8 the system default.
Derived from http://lkml.org/lkml/2007/8/31/246
Tested and works as expected.
Fine with me. I believe the original patch I sent went to -mm, so you
may
H. Peter Anvin ([EMAIL PROTECTED]) said:
> Hmmm...
>
> Personally I'd suggest making it the default unless overridden in
> /etc/sysctl.conf. My second preference would be a command-line option, not
> a compile-time default.
>
> This is 2007, after all, and it seems Unicode should be the
Jan Engelhardt ([EMAIL PROTECTED]) said:
> >dear all,
> >I'm trying to track down a problem on a Sun V40Z server with 4 network
> >devices grabbing random ethX device names. now, trying to force the
> >device names to what I want, I got a __tmpX form of device name,
> >which I think is a
Jan Engelhardt ([EMAIL PROTECTED]) said:
dear all,
I'm trying to track down a problem on a Sun V40Z server with 4 network
devices grabbing random ethX device names. now, trying to force the
device names to what I want, I got a __tmpX form of device name,
which I think is a
H. Peter Anvin ([EMAIL PROTECTED]) said:
Hmmm...
Personally I'd suggest making it the default unless overridden in
/etc/sysctl.conf. My second preference would be a command-line option, not
a compile-time default.
This is 2007, after all, and it seems Unicode should be the default,
Randy Dunlap ([EMAIL PROTECTED]) said:
> A diffstat would be nice.
Sure.
linux-2.6.22.noarch/drivers/char/Kconfig| 17 +
linux-2.6.22.noarch/drivers/char/keyboard.c |2 +-
linux-2.6.22.noarch/drivers/char/sysrq.c|4 ++--
linux-2.6.22.noarch/drivers/char/vt.c
terminal and the keyboard
driver.
Signed-off-by: Bill Nottingham <[EMAIL PROTECTED]>
diff -up linux-2.6.22.noarch/drivers/char/keyboard.c.foo
linux-2.6.22.noarch/drivers/char/keyboard.c
--- linux-2.6.22.noarch/drivers/char/keyboard.c.foo 2007-08-30
17:18:54.0 -0400
+++ linux-
terminal and the keyboard
driver.
Signed-off-by: Bill Nottingham [EMAIL PROTECTED]
diff -up linux-2.6.22.noarch/drivers/char/keyboard.c.foo
linux-2.6.22.noarch/drivers/char/keyboard.c
--- linux-2.6.22.noarch/drivers/char/keyboard.c.foo 2007-08-30
17:18:54.0 -0400
+++ linux-2.6.22.noarch
Randy Dunlap ([EMAIL PROTECTED]) said:
A diffstat would be nice.
Sure.
linux-2.6.22.noarch/drivers/char/Kconfig| 17 +
linux-2.6.22.noarch/drivers/char/keyboard.c |2 +-
linux-2.6.22.noarch/drivers/char/sysrq.c|4 ++--
linux-2.6.22.noarch/drivers/char/vt.c
Kay Sievers ([EMAIL PROTECTED]) said:
> Ah, ok, makes sense. Yeah, that weird "platform devices loads itself by
> the name" thing got disabled in the platform subsystem. It caused
> modprobe loops for other devices.
>
> The whole idea of issuing MODALIAS with plain module names instead of
>
Kay Sievers ([EMAIL PROTECTED]) said:
> It doesn't have any aliases, so seems it was never autoloaded.
It was - prior kernels loaded it via the uevent generated from
/devices/platform/pcspkr. Newer kernels seem to never actually
trigger a uevent from that (tested with a combination of
Kay Sievers ([EMAIL PROTECTED]) said:
It doesn't have any aliases, so seems it was never autoloaded.
It was - prior kernels loaded it via the uevent generated from
/devices/platform/pcspkr. Newer kernels seem to never actually
trigger a uevent from that (tested with a combination of
Kay Sievers ([EMAIL PROTECTED]) said:
Ah, ok, makes sense. Yeah, that weird platform devices loads itself by
the name thing got disabled in the platform subsystem. It caused
modprobe loops for other devices.
The whole idea of issuing MODALIAS with plain module names instead of
aliases
rds and support \
- for PCMCIA when used with airo_cs.");
+cards. Direct support for ISA/PCI/MPI cards and support \
+for PCMCIA when used with airo_cs.");
MODULE_LICENSE("Dual BSD/GPL");
MODULE_SUPPORTED_DEVICE("Aironet 4500, 4800 and Cisco 340/350");
module_param_array(io, i
when used with airo_cs.);
+cards. Direct support for ISA/PCI/MPI cards and support \
+for PCMCIA when used with airo_cs.);
MODULE_LICENSE(Dual BSD/GPL);
MODULE_SUPPORTED_DEVICE(Aironet 4500, 4800 and Cisco 340/350);
module_param_array(io, int, NULL, 0);
Signed-off-by: Bill Nottingham [EMAIL
Alexandre Oliva ([EMAIL PROTECTED]) said:
> > Wait, a signed filesystem image that happens to contain GPL code
> > is now a derived work? Under what sort of interpretation does *that*
> > occur?
>
> Is the signature not derived from the bits in the GPLed component, as
> much as it is derived
Alexandre Oliva ([EMAIL PROTECTED]) said:
> And since the specific implementation involves creating a derived work
> of the GPLed kernel (the signature, or the signed image, or what have
> you)
Wait, a signed filesystem image that happens to contain GPL code
is now a derived work? Under what
Alexandre Oliva ([EMAIL PROTECTED]) said:
> But how about inside the TiVO, so as to use Linux and the rest of the
> GNU/Linux distro put in there for an even better DVR experience?
>
> Sure, this might still be accomplished on another hardware platform.
> But the TiVO already has all the
Neshama Parhoti ([EMAIL PROTECTED]) said:
> But many of FSF's GNU projects are similar - for example GCC has
> contributors
> from many many companies and individuals, from which I presume there
> are who might object to GPLv3.
FSF requires copyright assignment to the FSF on things like the
Alexandre Oliva ([EMAIL PROTECTED]) said:
> > Sure, if they make any changes or fixes to Linux. Other than that,
> > only the same benefit that Microsoft get from Windows piracy - TiVo
> > employees become familiar with Linux and are more likely to use it
> > and maybe contribute more in another
Alexandre Oliva ([EMAIL PROTECTED]) said:
Sure, if they make any changes or fixes to Linux. Other than that,
only the same benefit that Microsoft get from Windows piracy - TiVo
employees become familiar with Linux and are more likely to use it
and maybe contribute more in another job
Neshama Parhoti ([EMAIL PROTECTED]) said:
But many of FSF's GNU projects are similar - for example GCC has
contributors
from many many companies and individuals, from which I presume there
are who might object to GPLv3.
FSF requires copyright assignment to the FSF on things like the
Alexandre Oliva ([EMAIL PROTECTED]) said:
But how about inside the TiVO, so as to use Linux and the rest of the
GNU/Linux distro put in there for an even better DVR experience?
Sure, this might still be accomplished on another hardware platform.
But the TiVO already has all the hardware
Alexandre Oliva ([EMAIL PROTECTED]) said:
And since the specific implementation involves creating a derived work
of the GPLed kernel (the signature, or the signed image, or what have
you)
Wait, a signed filesystem image that happens to contain GPL code
is now a derived work? Under what sort
Alexandre Oliva ([EMAIL PROTECTED]) said:
Wait, a signed filesystem image that happens to contain GPL code
is now a derived work? Under what sort of interpretation does *that*
occur?
Is the signature not derived from the bits in the GPLed component, as
much as it is derived from the
Greg KH ([EMAIL PROTECTED]) said:
> There are a number of distros out there right now who can support that
> option disabled. I'm pretty sure they are the following right now:
> Gentoo unstable (actually stable works now for me, but I'm not
>going to guarantee it
Greg KH ([EMAIL PROTECTED]) said:
There are a number of distros out there right now who can support that
option disabled. I'm pretty sure they are the following right now:
Gentoo unstable (actually stable works now for me, but I'm not
going to guarantee it just
Satyam Sharma ([EMAIL PROTECTED]) said:
> But yes, the kind of "fixes" you pointed out that _remove_ these conditions
> are definitely *not* what we would want to do.
I can see that - but I think it should be at least be brought up for each
warning, to determine either:
1) if it should be
iterations is unsigned, so it is impossible to get out of the loop
and return -ETIMEDOUT.
Signed-off-by: Bill Nottingham <[EMAIL PROTECTED]>
---
If the intention *is* to never fall out of the end of the loop, ignore
this, and just replace it with do {} while (1);.
--- drivers/scsi/q
Recent gcc versions emit warnings when unsigned variables are compared < 0 or
>= 0.
Signed-off-by: Bill Nottingham <[EMAIL PROTECTED]>
---
core/sysfs.c |2 +-
core/ucm.c |2 +-
core/ucma.c|2 +-
core/user_mad.c|5 ++---
core/uverbs_m
Recent gcc versions emit warnings when unsigned variables are compared < 0 or
>= 0.
Signed-off-by: Bill Nottingham <[EMAIL PROTECTED]>
---
aty/aty128fb.c |3 ---
aty/radeon_base.c|5 -
cirrusfb.c |5 -
fbmem.c |8 -
Recent gcc versions emit warnings when unsigned variables are compared < 0 or
>= 0.
Signed-off-by: Bill Nottingham <[EMAIL PROTECTED]>
---
mlx4/qp.c |3 +--
netxen/netxen_nic_niu.c |6 +++---
tulip/de2104x.c |1 -
3 files changed, 4 insertions(+),
Recent gcc versions emit warnings when unsigned variables are compared < 0 or
>= 0.
Signed-off-by: Bill Nottingham <[EMAIL PROTECTED]>
---
8021q/vlan.c |3 +--
dccp/probe.c |2 +-
ipv6/netfilter/nf_conntrack_l3
Recent gcc versions emit warnings when unsigned variables are compared < 0 or
>= 0.
Signed-off-by: Bill Nottingham <[EMAIL PROTECTED]>
---
filemap.c | 34 --
slub.c|2 --
2 files changed, 16 insertions(+), 20 deletions(-)
Patch
Recent gccs emit warnings when unsigned variables are compared < 0 or >= 0.
Signed-off-by: Bill Nottingham <[EMAIL PROTECTED]>
ac97/ac97_patch.c|3 +--
ali5451/ali5451.c|6 ++
ca0106/ca0106_proc.c |4 ++--
rme9652/rme9652.c|2 --
4 files changed,
Recent gccs emit warnings when unsigned variables are compared 0 or = 0.
Signed-off-by: Bill Nottingham [EMAIL PROTECTED]
ac97/ac97_patch.c|3 +--
ali5451/ali5451.c|6 ++
ca0106/ca0106_proc.c |4 ++--
rme9652/rme9652.c|2 --
4 files changed, 5 insertions(+), 10
Recent gcc versions emit warnings when unsigned variables are compared 0 or
= 0.
Signed-off-by: Bill Nottingham [EMAIL PROTECTED]
---
filemap.c | 34 --
slub.c|2 --
2 files changed, 16 insertions(+), 20 deletions(-)
Patch is noisy due to whitespace
Recent gcc versions emit warnings when unsigned variables are compared 0 or
= 0.
Signed-off-by: Bill Nottingham [EMAIL PROTECTED]
---
8021q/vlan.c |3 +--
dccp/probe.c |2 +-
ipv6/netfilter/nf_conntrack_l3proto_ipv6.c |3
Recent gcc versions emit warnings when unsigned variables are compared 0 or
= 0.
Signed-off-by: Bill Nottingham [EMAIL PROTECTED]
---
mlx4/qp.c |3 +--
netxen/netxen_nic_niu.c |6 +++---
tulip/de2104x.c |1 -
3 files changed, 4 insertions(+), 6 deletions
Recent gcc versions emit warnings when unsigned variables are compared 0 or
= 0.
Signed-off-by: Bill Nottingham [EMAIL PROTECTED]
---
aty/aty128fb.c |3 ---
aty/radeon_base.c|5 -
cirrusfb.c |5 -
fbmem.c |8
intelfb
Recent gcc versions emit warnings when unsigned variables are compared 0 or
= 0.
Signed-off-by: Bill Nottingham [EMAIL PROTECTED]
---
core/sysfs.c |2 +-
core/ucm.c |2 +-
core/ucma.c|2 +-
core/user_mad.c|5 ++---
core/uverbs_main.c |3 +--
core
iterations is unsigned, so it is impossible to get out of the loop
and return -ETIMEDOUT.
Signed-off-by: Bill Nottingham [EMAIL PROTECTED]
---
If the intention *is* to never fall out of the end of the loop, ignore
this, and just replace it with do {} while (1);.
--- drivers/scsi/qla2xxx
Satyam Sharma ([EMAIL PROTECTED]) said:
But yes, the kind of fixes you pointed out that _remove_ these conditions
are definitely *not* what we would want to do.
I can see that - but I think it should be at least be brought up for each
warning, to determine either:
1) if it should be ignored
Greg KH ([EMAIL PROTECTED]) said:
> > If interfaces have to change, so be it. But changing the rules for
> > using them years after it's implemented and then claiming "you didn't
> > read the instructions" is pretty lame.
>
> That documentation has been in the kernel tree for almost a full year:
Greg KH ([EMAIL PROTECTED]) said:
If interfaces have to change, so be it. But changing the rules for
using them years after it's implemented and then claiming you didn't
read the instructions is pretty lame.
That documentation has been in the kernel tree for almost a full year:
It has a
Greg KH ([EMAIL PROTECTED]) said:
> If you follow the rules in Documentation/ABI/testing/sysfs-class your
> program will not have any problems.
Oh, of *course*. We add interfaces and then claim years later,
after code has been written, "Oh, you shouldn't be using that!" in
documentation.
Greg KH ([EMAIL PROTECTED]) said:
If you follow the rules in Documentation/ABI/testing/sysfs-class your
program will not have any problems.
Oh, of *course*. We add interfaces and then claim years later,
after code has been written, Oh, you shouldn't be using that! in
documentation. Meanwhile,
Kay Sievers ([EMAIL PROTECTED]) said:
> >If you *do* try to use one of these names, the rename will succeed...
> >partway. The link in /sys/class/net is renamed, the directory is
> >not (as it obviously can't rename on top of whatever is already there.)
> >Various networking tools then break in
Kay Sievers ([EMAIL PROTECTED]) said:
If you *do* try to use one of these names, the rename will succeed...
partway. The link in /sys/class/net is renamed, the directory is
not (as it obviously can't rename on top of whatever is already there.)
Various networking tools then break in assorted
I was fiddling with the 'new' (no CONFIG_SYSFS_DEPRECATED) layout
and ethernet device names, and noticed that the new layout effectively
restricts the availability of certain device names.
By making a directory for the ethernet device name in the parent
device, you no longer can use any name that
I was fiddling with the 'new' (no CONFIG_SYSFS_DEPRECATED) layout
and ethernet device names, and noticed that the new layout effectively
restricts the availability of certain device names.
By making a directory for the ethernet device name in the parent
device, you no longer can use any name that
Gene Heskett ([EMAIL PROTECTED]) said:
> FWIW:
> [EMAIL PROTECTED] src]# python list-kernel-hardware.py
> Traceback (most recent call last):
> File "list-kernel-hardware.py", line 70, in ?
> ret = pciids_to_names(data)
> File "list-kernel-hardware.py", line 11, in pciids_to_names
>
Gene Heskett ([EMAIL PROTECTED]) said:
FWIW:
[EMAIL PROTECTED] src]# python list-kernel-hardware.py
Traceback (most recent call last):
File list-kernel-hardware.py, line 70, in ?
ret = pciids_to_names(data)
File list-kernel-hardware.py, line 11, in pciids_to_names
pciids =
Alistair John Strachan ([EMAIL PROTECTED]) said:
> > > Is it possible to use pata_mpiix (or pata_oldpiix) with an ICH4 IDE
> > > controller and boot off it?
> >
> > ata_piix (the SATA/PATA driver) deals with the ICH4. pata_mpiix is
> > specifically for the Intel MPIIX laptop chipset and
Rik van Riel ([EMAIL PROTECTED]) said:
> Maybe we should just educate users and teach them to
> avoid crazy unsupportable configurations and simply buy
> the hardware that has open drivers available?
Educating the users may help, but it's hard to do the
education once they've already bought the
Rik van Riel ([EMAIL PROTECTED]) said:
Maybe we should just educate users and teach them to
avoid crazy unsupportable configurations and simply buy
the hardware that has open drivers available?
Educating the users may help, but it's hard to do the
education once they've already bought the
Alistair John Strachan ([EMAIL PROTECTED]) said:
Is it possible to use pata_mpiix (or pata_oldpiix) with an ICH4 IDE
controller and boot off it?
ata_piix (the SATA/PATA driver) deals with the ICH4. pata_mpiix is
specifically for the Intel MPIIX laptop chipset and pata_oldpiix
Greg KH ([EMAIL PROTECTED]) said:
> An updated version is below.
If you're adding this, you should probably schedule EXPORT_SYMBOL_GPL
for removal at the same time, as this essentially renders that irrelevant.
That being said...
First, this is adding the measure at module load time. Any
Greg KH ([EMAIL PROTECTED]) said:
An updated version is below.
If you're adding this, you should probably schedule EXPORT_SYMBOL_GPL
for removal at the same time, as this essentially renders that irrelevant.
That being said...
First, this is adding the measure at module load time. Any
Jeff Garzik ([EMAIL PROTECTED]) said:
> It's always been the case that we remove Linux kernel code when the
> number of users (and more importantly, developers) drops to near-nil.
So, drivers/net/3c501.c?
Bill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Jeff Garzik ([EMAIL PROTECTED]) said:
It's always been the case that we remove Linux kernel code when the
number of users (and more importantly, developers) drops to near-nil.
So, drivers/net/3c501.c?
Bill
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of
The attached patch removes the '-' for '_' substitution from
depmod - this makes the names printed for modules in module.alias
match the actual names of the module files.
Bill
diff -ru depmod.c.old depmod.c
--- depmod.c2005-04-30 08:38:46.0 -0400
+++ depmod.c2005-09-08
The attached patch removes the '-' for '_' substitution from
depmod - this makes the names printed for modules in module.alias
match the actual names of the module files.
Bill
diff -ru depmod.c.old depmod.c
--- depmod.c2005-04-30 08:38:46.0 -0400
+++ depmod.c2005-09-08
Robert Love ([EMAIL PROTECTED]) said:
> Of late I have been working on a driver for the IBM Hard Drive Active
> Protection System (HDAPS), which provides a two-axis accelerometer and
> some other misc. data. The hardware is found on recent IBM ThinkPad
> laptops.
How does this relate to the
Robert Love ([EMAIL PROTECTED]) said:
Of late I have been working on a driver for the IBM Hard Drive Active
Protection System (HDAPS), which provides a two-axis accelerometer and
some other misc. data. The hardware is found on recent IBM ThinkPad
laptops.
How does this relate to the hdaps
When allocating a new VC with vgacon_init(), the font is
shared across all the VGA consoles. However, the font
mask was always set to the default value of zero in visual_init(),
even if we were using 512 character fonts at the time.
Moreover, code in vgacon.c:vga_do_font_op() didn't reset
the
When allocating a new VC with vgacon_init(), the font is
shared across all the VGA consoles. However, the font
mask was always set to the default value of zero in visual_init(),
even if we were using 512 character fonts at the time.
Moreover, code in vgacon.c:vga_do_font_op() didn't reset
the
Andrew Morton ([EMAIL PROTECTED]) said:
> > Test box is a 1.5GB laptop.
> >
> > In typical use, I would open a mailbox A, and then switch
> > to mailbox B. Immediately switching back to mailbox A, I
> > would find out it was no longer cached. (Using maildirs,
> > FWIW.)
> >
> > Looking at
Andrew Morton ([EMAIL PROTECTED]) said:
Test box is a 1.5GB laptop.
In typical use, I would open a mailbox A, and then switch
to mailbox B. Immediately switching back to mailbox A, I
would find out it was no longer cached. (Using maildirs,
FWIW.)
Looking at /proc/meminfo, I
When I upgraded from 2.6.11 to 2.6.12rc1, the VM started
behaving really badly with respect to caching.
Test box is a 1.5GB laptop.
In typical use, I would open a mailbox A, and then switch
to mailbox B. Immediately switching back to mailbox A, I
would find out it was no longer cached. (Using
When I upgraded from 2.6.11 to 2.6.12rc1, the VM started
behaving really badly with respect to caching.
Test box is a 1.5GB laptop.
In typical use, I would open a mailbox A, and then switch
to mailbox B. Immediately switching back to mailbox A, I
would find out it was no longer cached. (Using
Dave Jones ([EMAIL PROTECTED]) said:
> > [*] I don't know any details of the /proc incompatibility which davej
> > mentions, and I'd like to. That sounds like a screw-up.
>
> We changed the format of /proc/slabinfo. Running slabtop threw up
> an error message complaining that the format
Dave Jones ([EMAIL PROTECTED]) said:
[*] I don't know any details of the /proc incompatibility which davej
mentions, and I'd like to. That sounds like a screw-up.
We changed the format of /proc/slabinfo. Running slabtop threw up
an error message complaining that the format had
Jon Smirl ([EMAIL PROTECTED]) said:
> Is there a specific reason why they are blocked?
>
> For example I'm looking at making changes to DRM such that DRM will
> require the corresponding framebuffer driver to be loaded. If you back
> up further this is part of fixing X so that it won't mess
Jon Smirl ([EMAIL PROTECTED]) said:
Is there a specific reason why they are blocked?
For example I'm looking at making changes to DRM such that DRM will
require the corresponding framebuffer driver to be loaded. If you back
up further this is part of fixing X so that it won't mess with the
Jon Smirl ([EMAIL PROTECTED]) said:
> Why are all of the framebuffer drivers on the hotplug blacklist?
Well, that probably depends on your distribution. :)
Under Fedora (and RHEL), they're there because we generally
don't want to load them unless the user asked for them.
Bill
-
To unsubscribe
Jon Smirl ([EMAIL PROTECTED]) said:
Why are all of the framebuffer drivers on the hotplug blacklist?
Well, that probably depends on your distribution. :)
Under Fedora (and RHEL), they're there because we generally
don't want to load them unless the user asked for them.
Bill
-
To unsubscribe
Greg KH ([EMAIL PROTECTED]) said:
> I'd like to announce, yet-another-hotplug based userspace project:
> linux-ng. This collection of code replaces the existing linux-hotplug
> package with very tiny, compiled executable programs, instead of the
> existing bash scripts.
>
> It currently
Greg KH ([EMAIL PROTECTED]) said:
I'd like to announce, yet-another-hotplug based userspace project:
linux-ng. This collection of code replaces the existing linux-hotplug
package with very tiny, compiled executable programs, instead of the
existing bash scripts.
It currently provides the
The kernel in question is based on 2.6.11-rc2-bk4, FWIW.
Transcribed by hand. Happened when rsyncing data onto
a LVM-on-RAID1, sata_via controller. (root FS is on generic
VIA IDE).
slab: double free detected in cache 'size-128', objp 81000340bba8.
Kernel BUG at slab:2188
invalid operand:
The kernel in question is based on 2.6.11-rc2-bk4, FWIW.
Transcribed by hand. Happened when rsyncing data onto
a LVM-on-RAID1, sata_via controller. (root FS is on generic
VIA IDE).
slab: double free detected in cache 'size-128', objp 81000340bba8.
Kernel BUG at slab:2188
invalid operand:
(catching up...)
Alan Cox ([EMAIL PROTECTED]) said:
> 2.4.4-ac9
...
> o Further tulip updates (Jeff Garzik)
...
> 2.4.4-ac8
> o Tulip driver updates(Jeff Garzik)
These updates (sorry, haven't tracked down which of the two) conspire
(catching up...)
Alan Cox ([EMAIL PROTECTED]) said:
2.4.4-ac9
...
o Further tulip updates (Jeff Garzik)
...
2.4.4-ac8
o Tulip driver updates(Jeff Garzik)
These updates (sorry, haven't tracked down which of the two) conspire to
Jesper Juhl ([EMAIL PROTECTED]) said:
> I have made a patch against 2.4.4-ac8 that makes the change, it is
> below. I guess someone more knowledgeable than me can probably see if
> this is correct. If this is completely bogus, then please just disregard
> this email.
Yup, it's right. My bad.
Jesper Juhl ([EMAIL PROTECTED]) said:
I have made a patch against 2.4.4-ac8 that makes the change, it is
below. I guess someone more knowledgeable than me can probably see if
this is correct. If this is completely bogus, then please just disregard
this email.
Yup, it's right. My bad. :)
Jeff Garzik ([EMAIL PROTECTED]) said:
> Bill,
>
> Does the attached patch work for you?
Yup, works fine for me (compiled in.)
Bill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
The attached allows serial.c to work with my Xircom cardbus
ethernet+modem combo card. It doesn't get autodetected, because
the serial driver explicitly doesn't recognize anything with
more than one iomem region (the Xircom modem has two.)
If the serial driver is linked in statically, the delay
The attached allows serial.c to work with my Xircom cardbus
ethernet+modem combo card. It doesn't get autodetected, because
the serial driver explicitly doesn't recognize anything with
more than one iomem region (the Xircom modem has two.)
If the serial driver is linked in statically, the delay
Jeff Garzik ([EMAIL PROTECTED]) said:
Bill,
Does the attached patch work for you?
Yup, works fine for me (compiled in.)
Bill
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Jeff Dike ([EMAIL PROTECTED]) said:
> > > Is this sufficient to do driver development? TUN/TAP doesn't let me
> > > write
> > > ethernet drivers inside UML.
> > For ISDN not really. For SCSI yes - scsi generic would let you write a
> > virtual scsi adapter 'owning' some physical devices
>
>
Jeff Dike ([EMAIL PROTECTED]) said:
Is this sufficient to do driver development? TUN/TAP doesn't let me
write
ethernet drivers inside UML.
For ISDN not really. For SCSI yes - scsi generic would let you write a
virtual scsi adapter 'owning' some physical devices
Fine, so go
J . A . Magallon ([EMAIL PROTECTED]) said:
> > Can you back out the ide-cd changes Jens did and see if that fixes it ?
>
> Reverted the changes in ide-cd.[hc], and same result.
You want to back out the stuff from drivers/cdrom/cdrom.c; I backed
out the parts of the patch new there to ac10, and
J . A . Magallon ([EMAIL PROTECTED]) said:
Can you back out the ide-cd changes Jens did and see if that fixes it ?
Reverted the changes in ide-cd.[hc], and same result.
You want to back out the stuff from drivers/cdrom/cdrom.c; I backed
out the parts of the patch new there to ac10, and it
Klaus Reimer ([EMAIL PROTECTED]) said:
> Hi,
>
> > > modprobe opl3sa2 io=0x538 mss_io=0x530 mpu_io=0x330 irq=5 dma=1 dma2=0
> > > isapnp=0
> > It would be what you put in the io= parameter. 0x538 does *not* look
> > right.
>
> These are the sound-settings in the BIOS:
>
> WSS I/O: 0x530
>
Klaus Reimer ([EMAIL PROTECTED]) said:
> If I am doing this, I can't even load the module and I get the following
> message in syslog:
>
> 2001-03-29 18:13:14.184156500 {kern|err} kernel: opl3sa2: Control I/O port
> 0x0 not free
>
> What is that "control i/o port"? Is this normally 0x100?
I
Klaus Reimer ([EMAIL PROTECTED]) said:
> 2001-03-29 10:02:50.054774500 {kern|info} kernel: ad1848/cs4248 codec driver
> Copyright (C) by Hannu Savolainen 1993-1996
> 2001-03-29 10:02:50.070692500 {kern|notice} kernel: opl3sa2: No cards found
> 2001-03-29 10:02:50.070703500 {kern|notice} kernel:
Klaus Reimer ([EMAIL PROTECTED]) said:
2001-03-29 10:02:50.054774500 {kern|info} kernel: ad1848/cs4248 codec driver
Copyright (C) by Hannu Savolainen 1993-1996
2001-03-29 10:02:50.070692500 {kern|notice} kernel: opl3sa2: No cards found
2001-03-29 10:02:50.070703500 {kern|notice} kernel:
1 - 100 of 134 matches
Mail list logo
