Re: [PATCH] x86 (Linux Tiny): configure out support for some processors
On 2/8/08, Michael Opdenacker <[EMAIL PROTECTED]> wrote: > +config CPU_SUP_INTEL > + default y > + bool "Support Intel processors" if PROCESSOR_SELECT > + help > + This enables extended support for Intel processors > -obj-$(CONFIG_X86_32) += intel.o > +obj-$(CONFIG_CPU_SUP_INTEL)+= intel.o This config option should probably depend on X86_32. -- Taral <[EMAIL PROTECTED]> "Please let me know if there's any further trouble I can give you." -- Unknown -- 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/
Re: [PATCH] x86 (Linux Tiny): configure out support for some processors
On 2/8/08, Michael Opdenacker [EMAIL PROTECTED] wrote: +config CPU_SUP_INTEL + default y + bool Support Intel processors if PROCESSOR_SELECT + help + This enables extended support for Intel processors -obj-$(CONFIG_X86_32) += intel.o +obj-$(CONFIG_CPU_SUP_INTEL)+= intel.o This config option should probably depend on X86_32. -- Taral [EMAIL PROTECTED] Please let me know if there's any further trouble I can give you. -- Unknown -- 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/
Re: [PATCH] x86: fix unconditional arch/x86/kernel/pcspeaker.c compiling
On 1/18/08, Michael Opdenacker <[EMAIL PROTECTED]> wrote: > Do you mean "almost nothing"? It still allocates and adds a platform > device, and the corresponding function always gets called at boot time. Nothing significant then. I don't see any added functionality from this file. -- Taral <[EMAIL PROTECTED]> "Please let me know if there's any further trouble I can give you." -- Unknown -- 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/
Re: [PATCH] x86: fix unconditional arch/x86/kernel/pcspeaker.c compiling
On 1/18/08, Michael Opdenacker [EMAIL PROTECTED] wrote: Do you mean almost nothing? It still allocates and adds a platform device, and the corresponding function always gets called at boot time. Nothing significant then. I don't see any added functionality from this file. -- Taral [EMAIL PROTECTED] Please let me know if there's any further trouble I can give you. -- Unknown -- 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/
Re: [PATCH] x86: fix unconditional arch/x86/kernel/pcspeaker.c compiling
On 1/17/08, Michael Opdenacker <[EMAIL PROTECTED]> wrote: > Another issue would be that we would no longer be able > to load the speaker driver module from a kernel which > wasn't originally compiled with support for this module. Have you looked at pcspeaker.o? As far as I can tell, it does *nothing*. -- Taral <[EMAIL PROTECTED]> "Please let me know if there's any further trouble I can give you." -- Unknown -- 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/
Re: [PATCH] x86: fix unconditional arch/x86/kernel/pcspeaker.c compiling
On 1/17/08, Michael Opdenacker [EMAIL PROTECTED] wrote: Another issue would be that we would no longer be able to load the speaker driver module from a kernel which wasn't originally compiled with support for this module. Have you looked at pcspeaker.o? As far as I can tell, it does *nothing*. -- Taral [EMAIL PROTECTED] Please let me know if there's any further trouble I can give you. -- Unknown -- 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/
tty->name conversion?
I noticed that ps still relies on device numbers to determine tty, since /proc/*/stat only exports the device number. Is there any way to get the device name? I noticed that it is not present in tty_struct anywhere (proc_pid_stat() uses task->tty->device, which is a kdev_t). This would be useful to consider if we ever intend to create real unnumbered character/block devices. -- Taral <[EMAIL PROTECTED]> (This message is digitally signed. Please encrypt mail if possible.) "Any technology, no matter how primitive, is magic to those who don't understand it." -- Florence Ambrose PGP signature
tty-name conversion?
I noticed that ps still relies on device numbers to determine tty, since /proc/*/stat only exports the device number. Is there any way to get the device name? I noticed that it is not present in tty_struct anywhere (proc_pid_stat() uses task-tty-device, which is a kdev_t). This would be useful to consider if we ever intend to create real unnumbered character/block devices. -- Taral [EMAIL PROTECTED] (This message is digitally signed. Please encrypt mail if possible.) Any technology, no matter how primitive, is magic to those who don't understand it. -- Florence Ambrose PGP signature
tty kill character handling problems
I think the current echok/echoke/echoe handling is wrong. The following
patch should fix the problem, unless I've totally misunderstood this...
--- linux/drivers/char/n_tty.c.orig Fri May 11 21:45:48 2001
+++ linux/drivers/char/n_tty.c Fri May 11 22:00:52 2001
@@ -352,7 +352,7 @@
spin_unlock_irqrestore(>read_lock, flags);
return;
}
- if (!L_ECHOK(tty) || !L_ECHOKE(tty) || !L_ECHOE(tty)) {
+ if (!L_ECHOKE(tty)) {
spin_lock_irqsave(>read_lock, flags);
tty->read_cnt -= ((tty->read_head - tty->canon_head) &
(N_TTY_BUF_SIZE - 1));
--
Taral <[EMAIL PROTECTED]>
Please use PGP/GPG encryption to send me mail.
"Any technology, no matter how primitive, is magic to those who don't
understand it." -- Florence Ambrose
-
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/
tty kill character handling problems
I think the current echok/echoke/echoe handling is wrong. The following
patch should fix the problem, unless I've totally misunderstood this...
--- linux/drivers/char/n_tty.c.orig Fri May 11 21:45:48 2001
+++ linux/drivers/char/n_tty.c Fri May 11 22:00:52 2001
@@ -352,7 +352,7 @@
spin_unlock_irqrestore(tty-read_lock, flags);
return;
}
- if (!L_ECHOK(tty) || !L_ECHOKE(tty) || !L_ECHOE(tty)) {
+ if (!L_ECHOKE(tty)) {
spin_lock_irqsave(tty-read_lock, flags);
tty-read_cnt -= ((tty-read_head - tty-canon_head)
(N_TTY_BUF_SIZE - 1));
--
Taral [EMAIL PROTECTED]
Please use PGP/GPG encryption to send me mail.
Any technology, no matter how primitive, is magic to those who don't
understand it. -- Florence Ambrose
-
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/
