H. Peter Anvin writes:
Richard Gooch wrote:
We have this aliasing anyway. sg and sr are just one example. If you
care about conflicts, then make sure the drivers lock each other out.
It's got nothing to do with the mechanism to find out whether
something can behave like a CD-ROM or not.
H. Peter Anvin writes:
Richard Gooch wrote:
Erm, let's start again. My central point is that you can use devfs
names to reliably figure out what kind of device a FD is, as a cleaner
alternative to comparing major numbers. Therefore, I'm challenging the
notion that you need to reserve
code and your new release _before_ you do that.
The new code *can* automagically read and deal with 0.8 created VGDAs.
What are you refering too in detail here?
Yes. This is good
The important thing is that the external interface and on disk format dont
break - the code can be
Linus, patch is the first chunk of rootfs stuff. I've tried to
get it as small as possible - all it does is addition of absolute root
on ramfs and necessary changes to mount_root/change_root/sys_pivot_root
and follow_dotdot. Real root is mounted atop of the absolute one.
Surely this is
Whenever I boot (2.4.4-ac6) I get this error message if there is a zip
disk in the drive.
Does it work with ide-scsi ?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Richard Gooch wrote:
H. Peter Anvin writes:
Richard Gooch wrote:
Erm, let's start again. My central point is that you can use devfs
names to reliably figure out what kind of device a FD is, as a cleaner
alternative to comparing major numbers. Therefore, I'm challenging the
[Cc: list trimmed because I figure people are getting tired of us:-]
H. Peter Anvin writes:
Richard Gooch wrote:
H. Peter Anvin writes:
Richard Gooch wrote:
Erm, let's start again. My central point is that you can use devfs
names to reliably figure out what kind of device a
On Thu, 17 May 2001, Alan Cox wrote:
Are FireWire (and USB) disks always detected in the same order? Or does it
behave like ADB, where you never know which mouse/keyboard is which
mouse/keyboard?
USB disks are required (haha etc) to have serial numbers. Firewire similarly
has unique
cr:/speicher/src/u4ac9 $ ls -l mm/shmem.o*
-rw-r--r--1 cr users 154652 Mai 16 19:27 mm/shmem.o-tmpfs
-rw-r--r--1 cr users 180764 Mai 16 19:24 mm/shmem.o+tmpfs
cr:/speicher/src/u4ac9 $ ls -l fs/ramfs/ramfs.o
-rw-r--r--1 cr users 141452 Mai 16 19:27
I tested 2.4.4-ac9 today on A7V133 machine. It booted up, but can't stand
any load. It will deadlock (without oops) when the network/disk system faces
any load.
Let me guess 'ide=nodma' fixes that ?
There is also some new bug in VIA IDE driver. It misdetects cable as 80-w
when it's only
i'm guessing from your description that the missed event will be noticed
when the next socket arrives. i.e. if the server is pretty busy then the
missed events are not important. but if it's not a busy server, like a
hit every hour, then the missed event may be noticeable to browsers (as a
On Wed, 16 May 2001, H. Peter Anvin wrote:
Alan Cox wrote:
Are FireWire (and USB) disks always detected in the same order? Or does it
behave like ADB, where you never know which mouse/keyboard is which
mouse/keyboard?
USB disks are required (haha etc) to have serial numbers.
Richard Gooch wrote:
OK. How do you figure on dealing with the problem of multiple
high-level drivers talking to the same device? How does sr.o know
that this is also a CD-RW? How does sg.o know that this is also a
tape?
At some point something talks to the device -- in this case, it's
Alan Cox writes:
Argh! What I wrote in text is what I meant to say. The code didn't
match. No wonder people seemed to be missing the point. So the line of
code I actually meant was:
if (strcmp (buffer + len - 3, /cd) != 0) {
drivers/kitchen/bluetooth/vegerack/cd
its the cabbage
Argh! What I wrote in text is what I meant to say. The code didn't
match. No wonder people seemed to be missing the point. So the line of
code I actually meant was:
if (strcmp (buffer + len - 3, /cd) != 0) {
drivers/kitchen/bluetooth/vegerack/cd
its the cabbage dicer still ..
-
To
hpa wrote:
Alan Cox wrote:
Are FireWire (and USB) disks always detected in the same
order? Or does it
behave like ADB, where you never know which
mouse/keyboard is which mouse/keyboard?
USB disks are required (haha etc) to have serial numbers.
Firewire similarly has
On Thu, 17 May 2001, Alan Cox wrote:
Linus, patch is the first chunk of rootfs stuff. I've tried to
get it as small as possible - all it does is addition of absolute root
on ramfs and necessary changes to mount_root/change_root/sys_pivot_root
and follow_dotdot. Real root is mounted
Richard Gooch wrote:
Alan Cox writes:
Argh! What I wrote in text is what I meant to say. The code didn't
match. No wonder people seemed to be missing the point. So the line of
code I actually meant was:
if (strcmp (buffer + len - 3, /cd) != 0) {
Please throw any comments, questions, suggestions, hard objects this way...
First obvious comments
+ while (uCount-- != 0) {
+ unsigned short val_lo, val_hi;
+ cli();
+ val_lo = InWordDsp(DSP_MsaDataISLow);
+ val_hi =
The LANANA discussion has forked into a forest of vaguely related
discussions. If I am not mistaken the only real question is
how user space and kernel space communicate device identities.
Here user space is very different from users.
Devices have a device path and device contents.
For the
On Wed, May 16, 2001 at 08:05:38AM -0700, siva prasad wrote:
Is it true that the ipc calls like
msgget(),shmget()...
are not really system calls?
No, they all use a system call, but the system call is the same for all
functions.
Cos in the file asm/unistd.h where the
system calls are
On Wed, May 16, 2001 at 08:25:56PM +0300, Jussi Laako wrote:
I tested 2.4.4-ac9 today on A7V133 machine. It booted up, but can't stand
any load. It will deadlock (without oops) when the network/disk system faces
any load.
reset/clear CMOS with jumper. I get this kind of instability each time
when this happened, and I was not able to log in onto any console or
terminal afterwards (probably because tty_open failed very miserably
on the way?)
Its a deliberate debugging trap.
#if DEBUG
if (cachep-flags SLAB_POISON)
if (kmem_check_poison_obj(cachep, objp))
How well has the problem been nailed down? Could it be that it just
showed up first on VIA and the real cause (and fix) remains to be
discovered? Or does Serverworks somehow have an identical bug in
their chipset?
There is a notional off by one in the check at least by the rules of the
USB disks are required (haha etc) to have serial numbers. Firewire similarly
has unique disk identifiers.
How about for other device classes?
Keyboards and mice dont which is a real pig because it prevents you using
dual head, two usb keyboards and 2 usb mice for a dual user box (assuming
Yes, it's broken if someone writes a cabbage dicer driver and uses
cd as the leaf node name for devfs.
Yes, it's broken if someone writes a cabbage dicer driver and uses
the same major as the IDE CD-ROM or SCSI CD-ROM drivers.
The difference is one is a kernel interface magic cookie (be it
On Thu, May 17, 2001 at 12:26:12AM +0100, Alan Cox wrote:
Are FireWire (and USB) disks always detected in the same order? Or does it
behave like ADB, where you never know which mouse/keyboard is which
mouse/keyboard?
USB disks are required (haha etc) to have serial numbers. Firewire
[EMAIL PROTECTED] [[EMAIL PROTECTED]] wrote:
In principle the kernel could just number the devices it sees 1,2,...
and export information about them, so that user space can choose
the right number.
The part about exporting information is good. User space needs to
be able to ask if a certain
To inject a bit of concrete into this discussion, I note that block
devices with dynamically assigned don't work with CONFIG_DEVFS and
devfs=only. Block devices -require- majors currently, due to those
!@#!@# arrays. However, devfs_register_blkdev always returns zero when
devfs=only, even if
Gerard, LKML
The attached patch tweaks the sym53c8xx timeout timer handling a bit.
Is it correct?
It works with interrupts off (we need a reboot notifier to iterate the
hosts list, with IRQs off) and doesn't delay() 5 seconds in worst case.
Is there any reason this patch won't work? It seems
Just a me, too here. I see this when using the in-kernel driver. I'm
now using... 4.12, I think. At any rate, the error doesn't occur, or at
least occurs to rarely as to escape notice, with this driver. Might I
suggest the kernel's version be upgraded? The updated driver was posted
here on
I can't copy a file larger than 2 gigs to my vfat partition.
What gives? 2.4.4-ac5 kernel. My cp copies 2 gigs and then aborts.
$ echo foo file_on_vfat_partition
causes the shell to become unresponsive and consume lots of CPU time.
Felix
-
To unsubscribe from this list: send the line
Hello,
This is known issue. cmpci driver included in the kernel is way too old.
I'm using newer driver (revision 4.14) and it works just fine. It was
announced on lkml long time ago. Last time I checked there was even newer
driver - 5.64. The one in the kernel has version 2.41. Is it possible
I have been happily accumulating some files on an 80GB Maxtor HD sitting on
/dev/hdg mounted as /arc. There are 2 other drives on the HPT370 (KA7-100
MB with TY Bios) and 2 on the main mother board IDE controller. The system
is currently running 2.4.3-ac14. It has been solid as a rock and I
Followup to: [EMAIL PROTECTED]
By author:Felix von Leitner [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
I can't copy a file larger than 2 gigs to my vfat partition.
What gives? 2.4.4-ac5 kernel. My cp copies 2 gigs and then aborts.
$ echo foo file_on_vfat_partition
causes
On Wed, May 16, 2001 at 12:56:55PM -0700, Johannes Erdfelt wrote:
Could you try this patch? It applies on top of 2.2.20pre1
It also cleans up a couple of comments
That fixes it alright.
Shane
--
Shane Wegner: [EMAIL PROTECTED]
http://www.cm.nu/~shane/
PGP:
Julian Anastasov wrote:
eth0: Interrupt posted but not delivered -- IRQ blocked by another device?
This is a failure of the APIC interrupt controller in
the 2.4 kernel. You'll need to boot your kernel with
the `noapic' LILO option. Or run -ac kernels, which
have a software workaround which
Linus, I've done a bit more cleaning the device initialization
up (beginning of chr_dev_init()) and results were, well, interesting.
a) I2C stuff got converted to module_init() nicely. That took
a lot of cruft away.
b) init order is preserved. However, that worked only
[EMAIL PROTECTED] wrote:
[lots of sensible comments to get this discussion on track]
So we have: user space has file names and uses open() or mount().
Kernel space has device paths.
In principle the kernel could just number the devices it sees 1,2,...
and export information about them, so
OK, I know this is bizarre and probably some goof on my part, but it
is just too weird for me to guess at further:
My program write()s 2- and 4- byte chunks or data to a file (for a WAV
header). When the data being written contains an 0xff byte, it is
apparently written to disk as 2 bytes:
First this my configuration:
Kernel 2.4.4 / Athlon 650
May 17 05:38:45 m kernel: hdd: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
May 17 05:38:45 m kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
May 17 05:38:45 m kernel: ide1 at 0x170-0x177,0x376 on irq 15
May 17 05:38:45 m kernel: hda: 60036480
Hello
I have been trying to get 2.4.x to boot on my machine for sometime. I
finally got ac9 to boot today but I had to change the Processor Opts
from Athlon/K7/etc to PII/Celeron. I am running on an Iwill KK266 board
with a duron 800, 384 megs of RAM, SB Live X-Gamer, Adaptec 2910 and
2940UW,
On Wed, May 16, 2001, Shane Wegner [EMAIL PROTECTED] wrote:
On Wed, May 16, 2001 at 12:56:55PM -0700, Johannes Erdfelt wrote:
Could you try this patch? It applies on top of 2.2.20pre1
It also cleans up a couple of comments
That fixes it alright.
Excellent. Alan, could you apply the
I just patched my 2.2.18 kernel. After I did a make dep I got the
following message. Any ideas what does this mean?
md5sum: WARNING: 11 of 12 computed checksums did NOT match
Joe Acosta
home: [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
Please CC replies as I'm not subscribed.
I seem to be having some problems with sound ioctl's.
I've attached a short c file that opens /dev/dsp, prints the fd, tries
to issue SNDCTL_DSP_NONBLOCK ioctl, then does the same with /dev/audio.
Both calls to ioctl for NONBLOCK yield Invalid Invalid
Jeff Garzik writes:
Khachaturov, Vassilii wrote:
Can someone please confirm if my assumptions below are correct:
1) Unless someone specifically tampered with my driver's device
since the OS bootup, the mapping of the PCI base address registers
to virtual memory will remain the same (just as
On 16 May 2001 01:56:23 +0200, Tim Jansen wrote:
On Wednesday 16 May 2001 01:16, David Brownell wrote:
Only if it's augmented by additional device IDs, such as the
what 's the physical connection for this interface sort of
primitive that's been mentioned.
[...]
I suppose that for network
Fixed in the current sources, this was already fixed in 2.4.x
Later,
David S. Miller
[EMAIL PROTECTED]
-
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
401 - 448 of 448 matches
Mail list logo
