Re: wake up from a serial port

2007-09-12 Thread Michael Mauch
Guennadi Liakhovetski wrote: > Enable wakeup from serial ports, make it run-time configurable over sysfs, > e.g., > > echo enabled > /sys/devices/platform/serial8250.0/tty/ttyS0/power/wakeup Interesting, but how does that work from a user's/hardware perspective? Do I have to pull DSR/RI to

Re: wake up from a serial port

2007-09-12 Thread Michael Mauch
Guennadi Liakhovetski wrote: Enable wakeup from serial ports, make it run-time configurable over sysfs, e.g., echo enabled /sys/devices/platform/serial8250.0/tty/ttyS0/power/wakeup Interesting, but how does that work from a user's/hardware perspective? Do I have to pull DSR/RI to +12V?

Re: Serial ports rearranged in 2.6.22?

2007-08-13 Thread Michael Mauch
Bjorn Helgaas wrote: > On Saturday 11 August 2007 09:49:25 am Michael Mauch wrote: > > Yinghai Lu wrote: > > > > > On 8/10/07, Michael Mauch <[EMAIL PROTECTED]> wrote: > > > > > > > > With 2.6.22 I get the names <-> ports/irqs the othe

Re: Serial ports rearranged in 2.6.22?

2007-08-13 Thread Michael Mauch
Bjorn Helgaas wrote: On Saturday 11 August 2007 09:49:25 am Michael Mauch wrote: Yinghai Lu wrote: On 8/10/07, Michael Mauch [EMAIL PROTECTED] wrote: With 2.6.22 I get the names - ports/irqs the other way around: 00:08: ttyS0 at I/O 0x2f8 (irq = 3) is a 16550A 00:09

Re: Serial ports rearranged in 2.6.22?

2007-08-11 Thread Michael Mauch
Yinghai Lu wrote: > On 8/10/07, Michael Mauch <[EMAIL PROTECTED]> wrote: > > Hi, > > > > until 2.6.21, I had the normal assignments for ttyS0 and ttyS1: > > > > 00:08: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A > > 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is

Re: Serial ports rearranged in 2.6.22?

2007-08-11 Thread Michael Mauch
Yinghai Lu wrote: On 8/10/07, Michael Mauch [EMAIL PROTECTED] wrote: Hi, until 2.6.21, I had the normal assignments for ttyS0 and ttyS1: 00:08: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A With 2.6.22 I get the names - ports/irqs

Serial ports rearranged in 2.6.22?

2007-08-10 Thread Michael Mauch
Hi, until 2.6.21, I had the normal assignments for ttyS0 and ttyS1: 00:08: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A With 2.6.22 I get the names <-> ports/irqs the other way around: 00:08: ttyS0 at I/O 0x2f8 (irq = 3) is a 16550A 00:09: ttyS1 at

Serial ports rearranged in 2.6.22?

2007-08-10 Thread Michael Mauch
Hi, until 2.6.21, I had the normal assignments for ttyS0 and ttyS1: 00:08: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A With 2.6.22 I get the names - ports/irqs the other way around: 00:08: ttyS0 at I/O 0x2f8 (irq = 3) is a 16550A 00:09: ttyS1 at I/O

Re: Stable identification of identical USB hardware

2007-06-18 Thread Michael Mauch
Joerg Pommnitz wrote: > I want to be able to distinguish between two (or more) mostly > identical USB serial devices. The devices in question are UMTS modems. > AFAIK they are identical except for the SIM card and the point of > attachment. Externally the cards are CardBus devices with an

Re: Stable identification of identical USB hardware

2007-06-18 Thread Michael Mauch
Joerg Pommnitz wrote: I want to be able to distinguish between two (or more) mostly identical USB serial devices. The devices in question are UMTS modems. AFAIK they are identical except for the SIM card and the point of attachment. Externally the cards are CardBus devices with an integrated

Re: bug in 2.6.22-rc2: loop mount limited to one single iso image

2007-05-20 Thread Michael Mauch
Uwe Bugla wrote: > Andrey's path however (i. e. copying his attached version of loop.c into the > 2.6.22-rc2 kernel tree) led to: > > a. an incompilable kernel > b. endless messages trying to compile loop.c going like this (just a part of > them - not complete anyway!): > >

Re: bug in 2.6.22-rc2: loop mount limited to one single iso image

2007-05-20 Thread Michael Mauch
Uwe Bugla wrote: Andrey's path however (i. e. copying his attached version of loop.c into the 2.6.22-rc2 kernel tree) led to: a. an incompilable kernel b. endless messages trying to compile loop.c going like this (just a part of them - not complete anyway!): drivers/block/loop.c:1350:

Re: [PATCH] time locale in gen_initramfs_list.sh

2007-05-08 Thread Michael Mauch
Florian Fainelli wrote: > This is true. According to GNU fileutils changelog, the nearest Changelog > message regarding this option is : > > 2004-11-19 Alfred M. Szmidt <[EMAIL PROTECTED]> > >* src/ls.c (usage): Clarified description of --no-group (-G), >--human-readable

Re: [PATCH] time locale in gen_initramfs_list.sh

2007-05-08 Thread Michael Mauch
Florian Fainelli wrote: This is true. According to GNU fileutils changelog, the nearest Changelog message regarding this option is : 2004-11-19 Alfred M. Szmidt [EMAIL PROTECTED] * src/ls.c (usage): Clarified description of --no-group (-G), --human-readable (-h), --inode

/proc/interrupts vs. /proc/stat (and reality)

2001-04-29 Thread Michael Mauch
Hi, my /proc/interrupts doesn't show all the interrupts that have been used, /proc/stat (and hence procinfo) does. All of the devices work without problems. % cat /proc/interrupts /proc/stat && procinfo CPU0 0: 476919 XT-PIC timer 1: 12333

/proc/interrupts vs. /proc/stat (and reality)

2001-04-29 Thread Michael Mauch
Hi, my /proc/interrupts doesn't show all the interrupts that have been used, /proc/stat (and hence procinfo) does. All of the devices work without problems. % cat /proc/interrupts /proc/stat procinfo CPU0 0: 476919 XT-PIC timer 1: 12333 XT-PIC