* Re: [PATCH] 2.4.20-rmap15b
From: Rik van Riel @ 2002-12-17 21:50 UTC (permalink / raw)
To: Georg Nikodym; +Cc: linux-mm, linux-kernel
In-Reply-To: <200212161610.gBGGAuB7028719@localhost.localdomain>
On Mon, 16 Dec 2002, Georg Nikodym wrote:
> Incidentally, a colleague claimed to have seem this behaviour on a
> non-rmap 2.4.20.
> 1. Known behaviour?
> 2. Is there any data that I should be collecting that people are
> interested in?
> 3. Or should I just go back to 2.4.19-rmap14b (which did not trouble me
> in this way)?
The suspect is the disk elevator, which isn't scheduling requests
in a way to cause lower read latency, but is optimised more for
throughput. This results in some pauses.
I'll need to look into it.
regards,
Rik
--
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/ http://guru.conectiva.com/
Current spamtrap: <a href=mailto:"october@surriel.com">october@surriel.com</a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
^ permalink raw reply
* Re: MSN helper module
From: Filip Sneppe (Cronos) @ 2002-12-17 21:52 UTC (permalink / raw)
To: Carlos Fernandez Sanz; +Cc: netfilter-devel, Michael Richardson
In-Reply-To: <002801c2a5fb$1eb92660$152ea8c0@maincomp>
On Tue, 2002-12-17 at 19:35, Carlos Fernandez Sanz wrote:
> Yes, it needs some support for file tranmission, voice, etc. The protocol
> works a lot like FTP when using PORT (active) connections. The initiator
> client sends its IP address and a port number for the other end to connect
> to. For basic messaging it doesn't need any special NAT support, though -
> the reason being that all connections are outgoing and there are no related
> children connections.
>
> So it is not a lot of work but it needs to be done. I haven't found anything
> about it so I'm assuming no one has started any work, so I'll do it myself.
> Anyway it's pretty much a one man job.
>
Hi Carlos,
If you're thinking about this, these links will be of great help:
http://www.hypothetic.org/docs/msn/index.php
http://www.hypothetic.org/docs/msn/ietf_draft.php
http://www.venkydude.com/articles/msn.htm
I started working on a connection tracking module for this, but
really didn't go any further than adding the basic conntrack/nat
helper framework.
If you're really serious about this, I can send you a diff of
the basic conntrack/nat module to get you started. Just let me
know.
One thing to watch out for when writing a conntracker for
this, is that the MSN packet that should add an expectation for
a file transfer should contain data that like this:
...
Invitation-Command: ACCEPT
Invitation-Cookie: 33267
IP-Address: 10.44.102.65
Port: 6891
AuthCookie: 93301
...
Now the problem is that MSN also allows some chat-like protocol
over the same port.
If you're writing a conntracker, you must make sure that you
are not parsing the "Messaging" packets as file transfer
requests. Otherwise the code has a security vulnerability
where a specially crafted "Messaging" packet can add a firewall
connection expectation. When I realized my module was going to
have to detect this, I realized this wasn't going to be a
"weekend project" kind of thing and sort of gave up on it
for now. It would be great if you picked up the slack !
Regards,
Filip
^ permalink raw reply
* [BK PATCH] ACPI updates, mostly cosmetic
From: Grover, Andrew @ 2002-12-17 21:55 UTC (permalink / raw)
To: 'Linus Torvalds'; +Cc: acpi-devel-pyega4qmqnRoyOMFzWx49A
Hi Linus, please do a
bk pull http://linux-acpi.bkbits.net/linux-acpi
This will update the following files:
drivers/acpi/ac.c | 4
drivers/acpi/battery.c | 4
drivers/acpi/button.c | 4
drivers/acpi/dispatcher/dsfield.c | 87 ++++----
drivers/acpi/dispatcher/dsinit.c | 23 +-
drivers/acpi/dispatcher/dsmethod.c | 49 ++--
drivers/acpi/dispatcher/dsmthdat.c | 97 ++++-----
drivers/acpi/dispatcher/dsobject.c | 57 ++---
drivers/acpi/dispatcher/dsopcode.c | 147 +++++++-------
drivers/acpi/dispatcher/dsutils.c | 51 ++---
drivers/acpi/dispatcher/dswexec.c | 39 +--
drivers/acpi/dispatcher/dswload.c | 49 ++--
drivers/acpi/dispatcher/dswscope.c | 17 -
drivers/acpi/dispatcher/dswstate.c | 153 +++++++--------
drivers/acpi/ec.c | 2
drivers/acpi/events/evevent.c | 30 +-
drivers/acpi/events/evgpe.c | 97 ++++-----
drivers/acpi/events/evmisc.c | 53 ++---
drivers/acpi/events/evregion.c | 53 ++---
drivers/acpi/events/evrgnini.c | 85 ++++----
drivers/acpi/events/evsci.c | 17 -
drivers/acpi/events/evxface.c | 51 ++---
drivers/acpi/events/evxfevnt.c | 25 +-
drivers/acpi/events/evxfregn.c | 23 +-
drivers/acpi/executer/exconfig.c | 61 ++----
drivers/acpi/executer/exconvrt.c | 82 +++-----
drivers/acpi/executer/excreate.c | 75 +++----
drivers/acpi/executer/exdump.c | 127 ++++++------
drivers/acpi/executer/exfield.c | 31 +--
drivers/acpi/executer/exfldio.c | 109 +++++-----
drivers/acpi/executer/exmisc.c | 55 ++---
drivers/acpi/executer/exmutex.c | 45 ++--
drivers/acpi/executer/exnames.c | 49 ++--
drivers/acpi/executer/exoparg1.c | 93 ++++-----
drivers/acpi/executer/exoparg2.c | 59 ++---
drivers/acpi/executer/exoparg3.c | 37 +--
drivers/acpi/executer/exoparg6.c | 23 +-
drivers/acpi/executer/exprep.c | 77 +++----
drivers/acpi/executer/exregion.c | 109 +++++-----
drivers/acpi/executer/exresnte.c | 15 -
drivers/acpi/executer/exresolv.c | 51 ++---
drivers/acpi/executer/exresop.c | 33 +--
drivers/acpi/executer/exstore.c | 47 ++--
drivers/acpi/executer/exstoren.c | 37 +--
drivers/acpi/executer/exstorob.c | 25 +-
drivers/acpi/executer/exsystem.c | 47 ++--
drivers/acpi/executer/exutils.c | 45 ++--
drivers/acpi/fan.c | 4
drivers/acpi/hardware/hwacpi.c | 13 -
drivers/acpi/hardware/hwgpe.c | 41 +---
drivers/acpi/hardware/hwregs.c | 153 +++++++--------
drivers/acpi/hardware/hwsleep.c | 49 ++--
drivers/acpi/hardware/hwtimer.c | 25 +-
drivers/acpi/include/acconfig.h | 5
drivers/acpi/include/acdebug.h | 1
drivers/acpi/include/acdispat.h | 13 -
drivers/acpi/include/acevents.h | 3
drivers/acpi/include/acexcep.h | 1
drivers/acpi/include/acglobal.h | 31 +--
drivers/acpi/include/achware.h | 3
drivers/acpi/include/acinterp.h | 27 +-
drivers/acpi/include/aclocal.h | 67 +++---
drivers/acpi/include/acmacros.h | 69 ++----
drivers/acpi/include/acnamesp.h | 17 -
drivers/acpi/include/acobject.h | 151 +++++++-------
drivers/acpi/include/acoutput.h | 13 -
drivers/acpi/include/acparser.h | 1
drivers/acpi/include/acpi.h | 1
drivers/acpi/include/acpiosxf.h | 26 +-
drivers/acpi/include/acpixf.h | 18 -
drivers/acpi/include/acresrc.h | 101 ++++------
drivers/acpi/include/acstruct.h | 27 +-
drivers/acpi/include/actables.h | 21 --
drivers/acpi/include/actbl.h | 3
drivers/acpi/include/actbl1.h | 13 -
drivers/acpi/include/actbl2.h | 35 +--
drivers/acpi/include/actbl71.h | 15 -
drivers/acpi/include/actypes.h | 202 ++++++++++----------
drivers/acpi/include/acutils.h | 79 +++----
drivers/acpi/include/amlcode.h | 31 +--
drivers/acpi/include/amlresrc.h | 95 ++++-----
drivers/acpi/include/platform/acenv.h | 33 +--
drivers/acpi/include/platform/acgcc.h | 1
drivers/acpi/include/platform/aclinux.h | 1
drivers/acpi/namespace/nsaccess.c | 39 +--
drivers/acpi/namespace/nsalloc.c | 43 ++--
drivers/acpi/namespace/nsdump.c | 41 +---
drivers/acpi/namespace/nsdumpdv.c | 13 -
drivers/acpi/namespace/nseval.c | 49 ++--
drivers/acpi/namespace/nsinit.c | 27 +-
drivers/acpi/namespace/nsload.c | 28 +-
drivers/acpi/namespace/nsnames.c | 37 +--
drivers/acpi/namespace/nsobject.c | 37 +--
drivers/acpi/namespace/nsparse.c | 17 -
drivers/acpi/namespace/nssearch.c | 37 +--
drivers/acpi/namespace/nsutils.c | 127 ++++++------
drivers/acpi/namespace/nswalk.c | 31 +--
drivers/acpi/namespace/nsxfeval.c | 93 ++++-----
drivers/acpi/namespace/nsxfname.c | 15 -
drivers/acpi/namespace/nsxfobj.c | 15 -
drivers/acpi/osl.c | 26 +-
drivers/acpi/parser/psargs.c | 79 +++----
drivers/acpi/parser/psopcode.c | 11 -
drivers/acpi/parser/psparse.c | 73 +++----
drivers/acpi/parser/psscope.c | 41 +---
drivers/acpi/parser/pstree.c | 11 -
drivers/acpi/parser/psutils.c | 27 +-
drivers/acpi/parser/pswalk.c | 23 +-
drivers/acpi/parser/psxface.c | 13 -
drivers/acpi/power.c | 4
drivers/acpi/processor.c | 16 -
drivers/acpi/resources/rsaddr.c | 165 ++++++++--------
drivers/acpi/resources/rscalc.c | 65 +++---
drivers/acpi/resources/rscreate.c | 83 ++++----
drivers/acpi/resources/rsdump.c | 41 +---
drivers/acpi/resources/rsio.c | 119 +++++------
drivers/acpi/resources/rsirq.c | 91 ++++-----
drivers/acpi/resources/rslist.c | 43 ++--
drivers/acpi/resources/rsmemory.c | 133 ++++++-------
drivers/acpi/resources/rsmisc.c | 155 +++++++--------
drivers/acpi/resources/rsutils.c | 35 +--
drivers/acpi/resources/rsxface.c | 51 ++---
drivers/acpi/sleep.c | 4
drivers/acpi/tables/tbconvrt.c | 101 ++++------
drivers/acpi/tables/tbget.c | 61 ++----
drivers/acpi/tables/tbgetall.c | 27 +-
drivers/acpi/tables/tbinstal.c | 55 ++---
drivers/acpi/tables/tbrsdt.c | 35 +--
drivers/acpi/tables/tbutils.c | 27 +-
drivers/acpi/tables/tbxface.c | 71 +++----
drivers/acpi/tables/tbxfroot.c | 57 ++---
drivers/acpi/thermal.c | 4
drivers/acpi/utilities/utalloc.c | 157 +++++++--------
drivers/acpi/utilities/utcopy.c | 109 +++++-----
drivers/acpi/utilities/utdebug.c | 155 +++++++--------
drivers/acpi/utilities/utdelete.c | 29 +-
drivers/acpi/utilities/uteval.c | 43 ++--
drivers/acpi/utilities/utglobal.c | 91 ++++-----
drivers/acpi/utilities/utinit.c | 41 +---
drivers/acpi/utilities/utmath.c | 39 +--
drivers/acpi/utilities/utmisc.c | 151 +++++++-------
drivers/acpi/utilities/utobject.c | 85 ++++----
drivers/acpi/utilities/utxface.c | 47 ++--
143 files changed, 3572 insertions(+), 3709 deletions(-)
through these ChangeSets:
<agrover-qb8aLOKklSjp4P8CbLYnNQ@public.gmane.org> (02/12/17 1.888)
ACPI: More cosmetic changes to make the code more Linux-like
<agrover-qb8aLOKklSjp4P8CbLYnNQ@public.gmane.org> (02/12/17 1.887)
ACPI: remove non-Linux revision on files, and make types more Linux-like
<agrover-qb8aLOKklSjp4P8CbLYnNQ@public.gmane.org> (02/12/16 1.886)
ACPI: Fix oops on module insert/remove (Matthew Tippett)
-----------------------------
Andrew Grover
Intel Labs / Mobile Architecture
andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
^ permalink raw reply
* Re: mac address change on an eth alias
From: Petre Bandac @ 2002-12-17 21:55 UTC (permalink / raw)
To: pa3gcu, linux-newbie
In-Reply-To: <02121721144904.00388@unix.pa3gcu>
richard,
thanks for the answer; it is as you said, except I didn't manage to put 2
different macs
ifconfig eth0 hw ether 00:02:44:11:AA:AA
ifconfig eth0:1 hw ether 00:02:44:11:AA:AB
ifconfig eth0 some_IP netmask 255.255.255.0
ifconfig eth0:1 123.123.123.123 netmask 255.255.255.0
and the result is both have the same mac (the last one issued with ifconfig)
so I didn't get what I wanted - the mac of the alias being different than the
interface's; should I presume "no can do" ?
thanks,
petre
On Tuesday 17 December 2002 23:14 Anno Domini, pa3gcu wrote using one of his
keyboards:
> On Tuesday 17 December 2002 20:07, Petre Bandac wrote:
> > root@k:~# ifconfig eth0:1 123.123.123.123 netmask 255.255.255.0 hw ether
> > 00:E0:7D:02:C6:0C
> > SIOCSIFHWADDR: Device or resource busy
> > root@k:~#
> >
> > am I trying to do something impossible or is it only my NIC (Realtek
> > 8139) that can't do it ?
>
> AFAIK yes, at least the way you are doing it, you can however change a MAC
> adress before configuring the card.
>
> ifconfig eth0 00:E0:7D:02:C6:0C
> ifconfig eth0 123.123.123 netmask 255.255.255.0
>
> So what i am saying is, you cant change the MAC address when a IP# is
> assigned.
>
> I tested it on my eth0 interface but without aliasing, but i doubt if that
> is an issue here.
>
> > I want to have 2 ip's on the same interface - but with 2 different macs
> > ... why? because this is my testing server and, among others (dhcp, bind,
> > sendmail/postfix, asterisk, etc) I want to actually see how a mac address
> > can be changed ... if it's possible
>
> Down the IFC's, change the MAC(s), then configure the card and its aliases.
>
> > thank you for you patience,
> >
> > petre
--
23:50:25 up 7:20, 1 user, load average: 0.02, 0.06, 0.08
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply
* [ANNOUNCE] Intel PRO/100 software developer manual released
From: Feldman, Scott @ 2002-12-17 22:03 UTC (permalink / raw)
To: linux-kernel, netdev; +Cc: LOSTeam
Available at https://sourceforge.net/projects/e1000.
The full title is:
Intel 8255x 10/100 Mbps Ethernet Controller Family
Open Source Software Developer Manual
Revision 1.0
The manual is intended to support the maintenance of the e100 driver (or the
best driver for the PRO/100 networking hardware ;-). The manual covers the
82557, 82558, 82559, 82550, and 82551 Ethernet controllers.
I would like to thank Jeff Garzik for encouraging this publication, and for
having the patience to deal with the Intel machine.
I would also like to thank the Intel editors and reviewers: Carolyn
Abrigana, Larry Bates, Julie Donnelly, John Ronciak, Wen-Hwa Tao, Eli
Kupermann, David Valdez, Colleen Culbertson, and especially Glenn Begis for
not giving up.
-scott
^ permalink raw reply
* Re: [Linux-ia64] RTC support on ia64
From: Peter Chubb @ 2002-12-17 21:57 UTC (permalink / raw)
To: linux-ia64
In-Reply-To: <marc-linux-ia64-105590709805600@msgid-missing>
>>>>> "Alex" = Alex Williamson <alex_williamson@hp.com> writes:
Alex> Joel, Does this provide more functionality than the EFI RTC?
Alex> Concerns I have w/ it on ia64 is that the rtc driver assumes you
Alex> have a legacy rtc at the legacy irq and port address. This
Alex> won't work on HP zx1 boxes, the legacy hardware doesn't exist.
Alex> In the future, there's a possibility that the port address could
Alex> be allocated to non-legacy purposes. Maybe ACPI could tell you
Alex> if you have a legacy RTC, it could at least tell you if you
Alex> support PC/AT compatible interrupts. Thanks,
Yes it does. There's no way to get a regular interrupt into user
space from the EFI RTC.
I've been using the PMU to generate regular interrupts, and have a
locally-modified amlat benchmark that does that.
--
Dr Peter Chubb peterc@gelato.unsw.edu.au
You are lost in a maze of BitKeeper repositories, all almost the same.
^ permalink raw reply
* No booting with a Silicon Image 3112 SATA-Controller
From: Markus Wagner @ 2002-12-18 4:07 UTC (permalink / raw)
To: linux-kernel
Hi,
I got a PCI SATA-Controller with the SiI 3112 Chipset. I tried to get it
running with
2.4.19-ac4-ide ( from linux-ide.org )
2.4.20-ac1 and -ac2.
The support for the controller is compiled directly into the kernel.
Since I dont have a SATA-HDD, I am using a SATA to PATA dongle with an IBM
DTLA 307030 HDD.
When booting the 2.4.20-ac1/-ac2 kernel, the boot process stops at
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 132k freed
with no further action.
With Kernel 2.4.19-ac4-ide the system booted and crashed shortly after.
I tried the "ide=reveresed" kernel option with all kernels used.
Some info about my system:
MoBo: ECS Elitegroup K7S5A with AMD Athlon C 1400 ( SiS 735 Chipset )
The HDD ( IBM DTLA-307030 ) works without failure when using the onboard
Controller.
I tried to remove the network and the sound card to get a unique interrupt for
the controller but that didn't change things.
This is the Screen-Output when booting 2.4.20-ac2:
...
Uniform Multi-Platform E-IDE driver Revision: 7.00beta-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SIS5513: IDE controller at PCI slot 00:02.5
SIS5513: chipset revision 208
SIS5513: not 100% native mode: will probe irqs later
SiS735 ATA 100 controller
ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
SiI3112 Serial ATA: IDE controller at PCI slot 00:0b.0
PCI: Found IRQ 5 for device 00:0b.0
PCI: Sharing IRQ 5 with 00:11.0
SiI3112 Serial ATA: chipset revision 1
SiI3112 Serial ATA: not 100% native mode: will probe irqs later
ide2: MMIO-DMA at 0xe280ee00-0xe280ee07, BIOS settings: hde:pio, hdf:pio
ide3: MMIO-DMA at 0xe280ee08-0xe280ee0f, BIOS settings: hdg:pio, hdh:pio
hdc: CREATIVECD-RW RW121032E, ATAPI CD/DVD-ROM drive
hdd: CREATIVE CD5233E, ATAPI CD/DVD-ROM drive
hde: IBM-DTLA-307030, ATA DISK drive
hde: DMA disabled
hdg: no response (status = 0xfe)
ide2 at 0xe280ee80-0xe280ee87, 0xe280ee8a on IRQ 5
hde: host protected area => 1
hde: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(100)
ide-floppy driver 0.99.newide
Partition check:
hda: hda1 hda2 hda3 hda4
ide-floppy driver 0.99.newide
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 132k freed
Output of scripts/ver_linux:
Linux jupiter 2.4.20-ac2 #2 Die Dez 17 21:08:28 EST 2002 i686 unknown
Gnu C 2.96
Gnu make 3.79.1
util-linux 2.11n
mount 2.11n
modutils 2.4.18
e2fsprogs 1.27
reiserfsprogs 3.x.0j
Linux C Library 2.2.5
Dynamic linker (ldd) 2.2.5
Procps 2.0.7
Net-tools 1.60
Console-tools 0.3.3
Sh-utils 2.0.11
Modules Loaded sr_mod emu10k1 ac97_codec sound soundcore agpgart
nvidia natsemi ide-scsi scsi_mod ide-cd cdrom
cat /proc/pci ( with HDD on oboard IDE) :
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: Silicon Integrated Systems [SiS] 735 Host (rev 1).
Master Capable. Latency=32.
Non-prefetchable 32 bit memory at 0xd0000000 [0xd3ffffff].
Bus 0, device 1, function 0:
PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP (rev 0).
Master Capable. Latency=64. Min Gnt=10.
Bus 0, device 2, function 0:
ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 0).
Bus 0, device 2, function 5:
IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 208).
Master Capable. Latency=128.
I/O at 0xff00 [0xff0f].
Bus 0, device 11, function 0:
Unknown mass storage controller: PCI device 1095:3112 (CMD Technology Inc)
(rev 1).
IRQ 5.
Master Capable. Latency=64.
I/O at 0xd800 [0xd807].
I/O at 0xd400 [0xd403].
I/O at 0xd000 [0xd007].
I/O at 0xcc00 [0xcc03].
I/O at 0xc800 [0xc80f].
Non-prefetchable 32 bit memory at 0xcffffe00 [0xcfffffff].
Bus 0, device 15, function 0:
Ethernet controller: National Semiconductor Corporation DP83815
(MacPhyter) Ethernet Controller (rev 0).
IRQ 10.
Master Capable. Latency=64. Min Gnt=11.Max Lat=52.
I/O at 0xc400 [0xc4ff].
Non-prefetchable 32 bit memory at 0xcfffe000 [0xcfffefff].
Bus 0, device 17, function 0:
Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 8).
IRQ 5.
Master Capable. Latency=64. Min Gnt=2.Max Lat=20.
I/O at 0xc000 [0xc01f].
Bus 0, device 17, function 1:
Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 8).
Master Capable. Latency=64.
I/O at 0xdc00 [0xdc07].
Bus 1, device 0, function 0:
VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX] (rev
161).
IRQ 11.
Master Capable. Latency=248. Min Gnt=5.Max Lat=1.
Non-prefetchable 32 bit memory at 0xce000000 [0xceffffff].
Prefetchable 32 bit memory at 0xc0000000 [0xc7ffffff].
Hope you can make use of this
best regards,
Markus Wagner
^ permalink raw reply
* Re: mousewheel not working.
From: James Simmons @ 2002-12-17 23:04 UTC (permalink / raw)
To: Anders Fugmann; +Cc: linux-kernel
In-Reply-To: <3DFF070A.6010804@fugmann.dhs.org>
> I'm having troubles getting the mosuewheel on my logitech ps/2 mouseman+
> (model M-C48) to work, under 2.5.52. Do I need to add something special
> to the kernel boot parameters to instruct the driver that my mouse
> carries 5 buttons?
>
> dmesg:
> device class 'input': registering
> register interface 'mouse' with class 'input'
> mice: PS/2 mouse device common for all mice
> input: PS2++ Logitech Wheel Mouse on isa0060/serio1
>
> .config
>
> CONFIG_INPUT=y
> CONFIG_INPUT_MOUSE=y
> CONFIG_MOUSE_PS2=y
> # CONFIG_MOUSE_SERIAL is not set
Did you enable SERIO_8042 support ?
^ permalink raw reply
* Re: mac address change on an eth alias
From: pa3gcu @ 2002-12-17 22:06 UTC (permalink / raw)
To: Petre Bandac, pa3gcu, linux-newbie
In-Reply-To: <200212172355.32568.g38@rdsbv.ro>
On Tuesday 17 December 2002 21:55, Petre Bandac wrote:
> richard,
>
> thanks for the answer; it is as you said, except I didn't manage to put 2
> different macs
>
> ifconfig eth0 hw ether 00:02:44:11:AA:AA
> ifconfig eth0:1 hw ether 00:02:44:11:AA:AB
> ifconfig eth0 some_IP netmask 255.255.255.0
> ifconfig eth0:1 123.123.123.123 netmask 255.255.255.0
>
> and the result is both have the same mac (the last one issued with
> ifconfig)
>
> so I didn't get what I wanted - the mac of the alias being different than
> the interface's; should I presume "no can do" ?
I myself have never used aliasing, i do however need to spoof my MAC
sometimes on my laptop to be able to use it on other locations for my work.
However thats beside the point, as far as i can see if you set a different
IP# then the need for another MAC is (AFAIK) not nessasary.
If ARP's are a problem then setting static arps may be an answer, once more i
have no experiance with alising, possably Ray may have some advise for you.
>
> thanks,
>
> petre
>
--
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply
* RE: [PATCH] S4bios for 2.5.52.
From: Kai Germaschewski @ 2002-12-17 22:14 UTC (permalink / raw)
To: Grover, Andrew
Cc: 'Ducrot Bruno', linux-kernel, Pavel Machek, acpi-devel
In-Reply-To: <EDC461A30AC4D511ADE10002A5072CAD04C7A5B1@orsmsx119.jf.intel.com>
On Tue, 17 Dec 2002, Grover, Andrew wrote:
> > From: Ducrot Bruno [mailto:poup@poupinou.org]
> > This patch add s4bios support for 2.5.52.
> > echo 4 > /proc/acpi/sleep is for swsusp;
> > echo 4b > /proc/acpi/sleep is for s4bios.
>
> I still am not clear on why we would want s4bios in 2.5.x, since we have S4.
> Like you said, S4bios is easier to implement, but since Pavel has done much
> of the heavy lifting required for S4 proper, I don't see the need.
Let me counter this, I have to admit that I didn't try the patch yet, but
my laptop does S4 BIOS, and I'd definitely prefer that to swsusp, since
it's much faster and also I somewhat have more faith into S4 BIOS than
swsusp (as in: after resuming, it'll most likely either work or crash, but
not cause any weird kinds of corruption). Since it does not need not much
more to support it than S3, I don't see why you wouldn't want to give
users the option?
--kai
^ permalink raw reply
* Re: mousewheel not working.
From: Anders Fugmann @ 2002-12-17 22:16 UTC (permalink / raw)
To: James Simmons; +Cc: linux-kernel
In-Reply-To: <Pine.LNX.4.33.0212171503430.1879-100000@maxwell.earthlink.net>
[-- Attachment #1: Type: text/plain, Size: 175 bytes --]
James Simmons wrote:
>
> Did you enable SERIO_8042 support ?
>
>
Yes.
I have attached my .config in case my sections from .config was not enough.
Regards
Anders Fugmann
[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 20830 bytes --]
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_SWAP=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
#
# General setup
#
CONFIG_NET=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
CONFIG_KMOD=y
#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_X86_MCE_P4THERMAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_SOFTWARE_SUSPEND is not set
#
# ACPI Support
#
CONFIG_ACPI=y
# CONFIG_ACPI_HT_ONLY is not set
CONFIG_ACPI_BOOT=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_APM is not set
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_SCx200 is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set
#
# Executable file formats
#
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
# CONFIG_PNP is not set
#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_LBD is not set
#
# ATA/ATAPI/MFM/RLL device support
#
CONFIG_IDE=y
#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_IDE_TASK_IOCTL=y
#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_GENERIC=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDE_TCQ is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_PCI_WIP=y
CONFIG_IDEDMA_NEW_DRIVE_LISTINGS=y
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NFORCE is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
CONFIG_IDEDMA_AUTO=y
CONFIG_IDEDMA_IVB=y
CONFIG_BLK_DEV_IDE_MODES=y
#
# SCSI device support
#
# CONFIG_SCSI is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_INET_ECN=y
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_XFRM_USER is not set
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_UNCLEAN=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_MIRROR=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_NAT_LOCAL=y
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
# CONFIG_IPV6 is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
CONFIG_IP_SCTP=m
# CONFIG_SCTP_ADLER32 is not set
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_CSZ=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_INGRESS=m
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_POLICE=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
#
# Network device support
#
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
CONFIG_8139TOO=y
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_NET_POCKET is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Token Ring devices (depends on LLC=y)
#
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
CONFIG_SHAPER=m
#
# Wan interfaces
#
# CONFIG_WAN is not set
#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set
#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set
#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_USB=y
# CONFIG_JOYSTICK_IFORCE_232 is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDDLER is not set
# CONFIG_INPUT_JOYDUMP is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_UINPUT=m
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
#
# I2C support
#
# CONFIG_I2C is not set
#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set
#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_NOWAYOUT=y
CONFIG_SOFT_WATCHDOG=y
# CONFIG_WDT is not set
# CONFIG_WDTPCI is not set
# CONFIG_PCWATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_I810_TCO is not set
# CONFIG_MIXCOMWD is not set
# CONFIG_SCx200_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_INTEL_RNG is not set
CONFIG_AMD_RNG=m
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_VIA is not set
CONFIG_AGP_AMD=y
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_AMD_8151 is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FAT_FS=m
# CONFIG_MSDOS_FS is not set
CONFIG_VFAT_FS=m
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_JFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
# CONFIG_DEVPTS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_EXT2_FS is not set
# CONFIG_SYSV_FS is not set
CONFIG_UDF_FS=m
# CONFIG_UFS_FS is not set
# CONFIG_XFS_FS is not set
#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V4=y
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
# CONFIG_CIFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_AFS_FS is not set
CONFIG_FS_MBCACHE=y
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
#
# Sound
#
CONFIG_SOUND=y
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=y
CONFIG_SND_SEQUENCER=y
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
# CONFIG_SND_SEQUENCER_OSS is not set
CONFIG_SND_RTCTIMER=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
CONFIG_SND_MPU401=y
#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
CONFIG_SND_CMIPCI=y
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set
#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
CONFIG_USB_DYNAMIC_MINORS=y
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_UHCI_HCD=m
#
# USB Device Class drivers
#
CONFIG_USB_AUDIO=m
CONFIG_USB_BLUETOOTH_TTY=m
CONFIG_USB_MIDI=m
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
#
# SCSI support is needed for USB Storage
#
#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
CONFIG_HID_FF=y
CONFIG_HID_PID=y
# CONFIG_LOGITECH_FF is not set
CONFIG_USB_HIDDEV=y
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
CONFIG_USB_AIPTEK=m
CONFIG_USB_WACOM=m
CONFIG_USB_POWERMATE=m
CONFIG_USB_XPAD=m
#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_SCANNER=m
#
# USB Multimedia devices
#
CONFIG_USB_DABUSB=m
#
# Video4Linux support is needed for USB Multimedia device support
#
#
# USB Network adaptors
#
CONFIG_USB_CATC=m
CONFIG_USB_CDCETHER=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET=m
#
# USB port drivers
#
#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=y
# CONFIG_USB_SERIAL_DEBUG is not set
# CONFIG_USB_SERIAL_CONSOLE is not set
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KEYSPAN_USA28=y
CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
CONFIG_USB_SERIAL_KEYSPAN_USA19=y
CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_SAFE=m
# CONFIG_USB_SERIAL_SAFE_PADDED is not set
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_EZUSB=y
#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI26=m
CONFIG_USB_TIGL=m
CONFIG_USB_AUERSWALD=m
CONFIG_USB_RIO500=m
CONFIG_USB_BRLVGER=m
CONFIG_USB_LCD=m
CONFIG_USB_TEST=m
#
# Bluetooth support
#
# CONFIG_BT is not set
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_KALLSYMS is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_X86_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
#
# Security options
#
CONFIG_SECURITY=y
CONFIG_SECURITY_CAPABILITIES=y
CONFIG_SECURITY_ROOTPLUG=m
#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
# CONFIG_CRYPTO_TEST is not set
#
# Library routines
#
CONFIG_CRC32=m
CONFIG_X86_BIOS_REBOOT=y
^ permalink raw reply
* Re: Alcatel speedtouch USB driver and SMP.
From: romieu @ 2002-12-17 22:20 UTC (permalink / raw)
To: Colin Paul Adams; +Cc: linux-kernel
In-Reply-To: <m3adj6gwus.fsf@colina.demon.co.uk>
Colin Paul Adams <colin@colina.demon.co.uk> :
[...]
> So, is anyone using it on SMP?
drivers/usb/misc/speedtouch.c::udsl_atm_ioctl() calls put_user() and
atm ioctls are issued with spinlock held (see net/atm/common.c::atm_ioctl()).
--
Ueimor
^ permalink raw reply
* RE: [PATCH] S4bios for 2.5.52.
From: Kai Germaschewski @ 2002-12-17 22:14 UTC (permalink / raw)
To: Grover, Andrew
Cc: 'Ducrot Bruno', linux-kernel-u79uwXL29TY76Z2rM5mHXA,
Pavel Machek, acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
In-Reply-To: <EDC461A30AC4D511ADE10002A5072CAD04C7A5B1-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
On Tue, 17 Dec 2002, Grover, Andrew wrote:
> > From: Ducrot Bruno [mailto:poup-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org]
> > This patch add s4bios support for 2.5.52.
> > echo 4 > /proc/acpi/sleep is for swsusp;
> > echo 4b > /proc/acpi/sleep is for s4bios.
>
> I still am not clear on why we would want s4bios in 2.5.x, since we have S4.
> Like you said, S4bios is easier to implement, but since Pavel has done much
> of the heavy lifting required for S4 proper, I don't see the need.
Let me counter this, I have to admit that I didn't try the patch yet, but
my laptop does S4 BIOS, and I'd definitely prefer that to swsusp, since
it's much faster and also I somewhat have more faith into S4 BIOS than
swsusp (as in: after resuming, it'll most likely either work or crash, but
not cause any weird kinds of corruption). Since it does not need not much
more to support it than S3, I don't see why you wouldn't want to give
users the option?
--kai
^ permalink raw reply
* [LARTC] WonderShaper on LAN link kills to-host speed
From: Kenneth Porter @ 2002-12-17 22:15 UTC (permalink / raw)
To: lartc
I tried installing the WonderShaper on my internal link, mostly to get the
SFQ installed. I set uplink and downlink to 100000 to match the link speed
and changed the bandwidth on the cbq line to 100mbit. This killed transfer
speed *to* the box, knocking it from 30-40 Mbps down to about 800 kbps.
Commenting out just the ingress control restored the speed.
What about the ingress policer would do that?
Here's the effective line after shell expansions:
tc filter add dev eth0 parent ffff: protocol ip prio 50 u32 match ip src \
0.0.0.0/0 police rate 100000kbit burst 10k drop flowid :1
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply
* RE: [PATCH] S4bios for 2.5.52.
From: Grover, Andrew @ 2002-12-17 22:24 UTC (permalink / raw)
To: 'Kai Germaschewski'
Cc: 'Ducrot Bruno', linux-kernel, Pavel Machek, acpi-devel
> From: Kai Germaschewski [mailto:kai@tp1.ruhr-uni-bochum.de]
> > I still am not clear on why we would want s4bios in 2.5.x,
> since we have S4.
> > Like you said, S4bios is easier to implement, but since
> Pavel has done much
> > of the heavy lifting required for S4 proper, I don't see the need.
>
> Let me counter this, I have to admit that I didn't try the
> patch yet, but
> my laptop does S4 BIOS, and I'd definitely prefer that to
> swsusp, since
> it's much faster and also I somewhat have more faith into S4 BIOS than
> swsusp (as in: after resuming, it'll most likely either work
> or crash, but
> not cause any weird kinds of corruption). Since it does not
> need not much
> more to support it than S3, I don't see why you wouldn't want to give
> users the option?
Ok that's reasonable.
My belief is that S4bios is a stopgap measure until S4 gets better. That
said, I think you are right - it should go in for now, and then at some
point in the future someone will say, "S4bios?? who needs *that* anymore??"
and it will get pulled out. ;-)
So I'll look to merge it, unless someone upstream beats me to it.
Regards -- Andy
^ permalink raw reply
* Re: Domain transition
From: Brian May @ 2002-12-17 22:16 UTC (permalink / raw)
To: Russell Coker; +Cc: SELinux
In-Reply-To: <200212171431.52724.russell@coker.com.au>
On Tue, Dec 17, 2002 at 02:31:52PM +0100, Russell Coker wrote:
> On Tue, 17 Dec 2002 12:42, Brian May wrote:
> > > Kerberos still isn't safe, proxying the telnet protocol and hijacking it
> > > is not overly difficult...
> >
> > Do you have a reference?
>
> Is one really needed?
>
> Redirecting a port 23 connection to one on the local machine and then
> establishing a new connection to the server is quite easy if you control a
> router. Going from that to taking over an idle session is quite easy.
Not if you have encryption enabled...
--
Brian May <bam@snoopy.apana.org.au>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
^ permalink raw reply
* Echo Gals news: GPL!
From: David Olofson @ 2002-12-17 22:17 UTC (permalink / raw)
To: alsa-devel
I was just informed that the next release of the Echo driver source
will be under the GPL.
So, it looks like I'm gonna' get that Layla moving again! :-)
//David Olofson - Programmer, Composer, Open Source Advocate
.- The Return of Audiality! --------------------------------.
| Free/Open Source Audio Engine for use in Games or Studio. |
| RT and off-line synth. Scripting. Sample accurate timing. |
`---------------------------> http://olofson.net/audiality -'
--- http://olofson.net --- http://www.reologica.se ---
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
^ permalink raw reply
* RE: [PATCH] S4bios for 2.5.52.
From: Grover, Andrew @ 2002-12-17 22:24 UTC (permalink / raw)
To: 'Kai Germaschewski'
Cc: 'Ducrot Bruno', linux-kernel-u79uwXL29TY76Z2rM5mHXA,
Pavel Machek, acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
> From: Kai Germaschewski [mailto:kai-K3FV8rsiL1oTdZ4mcS17cL1bcanuHkqH@public.gmane.org]
> > I still am not clear on why we would want s4bios in 2.5.x,
> since we have S4.
> > Like you said, S4bios is easier to implement, but since
> Pavel has done much
> > of the heavy lifting required for S4 proper, I don't see the need.
>
> Let me counter this, I have to admit that I didn't try the
> patch yet, but
> my laptop does S4 BIOS, and I'd definitely prefer that to
> swsusp, since
> it's much faster and also I somewhat have more faith into S4 BIOS than
> swsusp (as in: after resuming, it'll most likely either work
> or crash, but
> not cause any weird kinds of corruption). Since it does not
> need not much
> more to support it than S3, I don't see why you wouldn't want to give
> users the option?
Ok that's reasonable.
My belief is that S4bios is a stopgap measure until S4 gets better. That
said, I think you are right - it should go in for now, and then at some
point in the future someone will say, "S4bios?? who needs *that* anymore??"
and it will get pulled out. ;-)
So I'll look to merge it, unless someone upstream beats me to it.
Regards -- Andy
^ permalink raw reply
* Re: [patch 2.5] PCI: kill pdev_enable_device()
From: Jeff Garzik @ 2002-12-17 22:31 UTC (permalink / raw)
To: Ivan Kokshaysky; +Cc: Linus Torvalds, linux-kernel
In-Reply-To: <20021217201938.A16940@jurassic.park.msu.ru>
Ivan Kokshaysky wrote:
> - So, if we don't touch the PCI command registers, there is no point in
> using pdev_enable_device(). Most drivers properly use
> pci_enable_device() anyway.
Not only that, a driver _should_ be calling pci-enable-device, it's an
API requirement. J Random Driver should have a good reason _not_ to
call pci_enable_device() ...
^ permalink raw reply
* Re: slave_destroy called in scsi_scan.c:scsi_probe_and_add_lun()
From: Doug Ledford @ 2002-12-17 22:24 UTC (permalink / raw)
To: Justin T. Gibbs; +Cc: linux-scsi
In-Reply-To: <797140000.1040156703@aslan.btc.adaptec.com>
On Tue, Dec 17, 2002 at 01:25:07PM -0700, Justin T. Gibbs wrote:
> >> So, you cannot rely on slave_destroy as an indication of a device really
> >> going away in the physical sense.
> >
> > No, you can. In the code snippet above you might be destroying something
> > at scsi0:0:0:0 and adding something at scsi0:0:1:0. Regardless, the
> > thing being destroyed is in fact going away permanently.
>
> The SDEV, yes. The physical device, not necessarily.
We're arguing semantics here. On the extra slave_destroy() calls, one of
two things will be true. A) there was a device present, another
slave_alloc() for this exact device has already been made, and we are now
just destroying the extraneous reference to the device or B) there was no
device and the destroy is in fact a real destroy event. So, if in your
slave_alloc() area you are attaching a scsi_device struct to other
internal state information, you could in fact do a refcount attachement,
and then on any transition from non-0 to 0 in the refcount you would in
fact have a true destroy event.
Now, that being said, I agree that the above is utter crap. It's dictated
by historical fact in the scsi_scan.c code. The scenario you point out
below is actually what I would prefer and would have done, but I can in
fact see the point that creating a new block queue for each device you
scan is insane, especially on some fiber channel controllers doing
probe_all_luns on very high lun limits. At bootup I wouldn't really care
about the overhead of creating all these queues. I'm more concerned with
hot plug events that bring a new controller online when a system is
already under some amount of memory pressure. My concern is that in that
situation, allocating 256 block layer request structs plus a few other
items for each device/lun we scan might in fact be excessive memory churn.
Anyone who wishes is free to convince me otherwise, in which case we can
fix the scan code properly and make it do like you are suggesting.
> The concern is that
> the API should only be called when the system is saying "physical device
> gone", not due to some quirk in how the mid-layer manages its data objects.
Well, whatever other meaning you want to attach to it, it *is* about data
objects. That's why it's called slave_alloc()/slave_destroy() which are
standard object manipulation terms. One of the reasons I did this was so
that in my driver I could yank out a bunch of host structs of the form
unsigned char queue_depth[MAX_TARGETS][MAX_LUNS};
and instead add a new struct aic_dev_data that I attach directly to
device->hostdata during slave_alloc(), and in that struct aic_dev_data
goes *all* the state data needed for that device. It resulted in a not
insignificant reduction in memory foot print for the driver. And, once
you start talking about higher and higher lun values, need I again mention
fiber channel here, keeping complete tables like that becomes wasteful in
the extreme. So, the actual *primary* reason for adding this interface
was exactly this manipulation of data objects. The secondary use that a
slave_destroy() event can trigger a device shutdown sequence in your
driver was a bonus, but because of hokey crap in the scsi scan code it's a
bonus that requires you refcount things instead of just assuming that a
slave_destroy() is permanent. My driver doesn't have that particular
problem because when the scsi mid layer allocates the new sdev and calls
slave_alloc(), I create a new struct, attach it, init it, then treat the
two sdevs as totally independant entities, so when the destroy comes in on
the probe device, all I have to do is kfree() my aic_dev stuff. If I were
to hook this for actual device shut down commands, then I would have to
jump through the same hoops as you (or else do something simpler, like
have slave_configure() set a AHC_DEVICE_RUNNING flag in your device state
and on slave_destroy() only bother performing any shutdown operations if
that flag is set).
> In otherwords, the mid-layer could just as easily free the sdev every
> time a probe fails, retain the already allocated sdev for the "found
> device", and allocate a new sdev for each new probe. This would avoid
> callbacks for physical devices that Linux has successfully probed.
>
> > Whenever we do
> > find a device, we actually allocate a new device struct identical to our
> > current device struct and call slave_alloc() for the newly created
> > device. So, whenever we find a new device, there will be a momentary
> > point in time at which two device structs will exist that point to the
> > same device. After the new device is allocated and set up, the original
> > sdevscan device is simply renumbered in place (by updating the target or
> > lun value) and then we call slave_destroy()/slave_alloc() so that the
> > low level driver can also update their target/lun values to match.
>
> Actually, this danger only exists if the low lever driver attaches
> something to the SDEV and/or has a pointer to the SDEV. The device
> at a particular target/lun is still the same device. The little dance
> performed in the mid-layer can't change that.
Hanging data structs off of the sdev->hostdata place holder is exactly
what this was intended to support.
> >> In SPI, for example, the driver can only
> >> tell that the device is gone if a command is issued to it. I had hoped
> >> that I could detect hot-pull/scsi-remove-single-device operations via
> >> this callback.
> >
> > You can. On any device we find, at device tear down time your
> > slave_destroy() entry point will get called right before the device
> > struct itself is kfree()ed.
>
> The problem is that the SDEV lifetime is not representative to the
> device's lifetime.
Only true for the sdev used to scan the devices. The use of either
refcounting or the simple flag set during slave_configure() either one
would solve your problem. And yes, I do agree that this answer is ugly,
but I need someone to convince me that block queue allocations on a live
and possibly busy machine aren't something that could cause problems
before I would change it myself.
Well, that or I need Jens to clean up the block layer allocation code so
that it only allocates one request at block queue init time and from then
on does lazy request allocations once the device needs them, similar to
what I did with the scsi command blocks. That way, strong memory pressure
and huge, wasted allocations would be avoided. It would also make sense
to me if Jens would add a feature to the block layer so that when we
adjust our scsi queue depth on our devices that we can indicate our queue
depth to the block layer so that the block layer could adjust its request
depth to some amount > our queue depth for optimum merging and what not.
Dynamic changes to this depth at the block layer would also be nice. If
these changes were made, then I would rip the damn scsi_scan code apart
and put it back together right using the exact semantics you outlined
above.
> Actually, the slave_configure() is postponed until way after the inquiry
> data is retrieved. If slave_congigure() were called as soon as the
> device were properly detected, the slave_destroy() in scsi_scan.c would
> be destroying a device that had been slave_configured.
Heh, if you write your code that way, then yes. In my driver it would
not:
alloc_sdev(sdev1)
slave_alloc(sdev1) - attaches struct to sdev
INQUIRY
found device!
alloc_sdev(sdev2)
copy state from sdev1 to sdev2
slave_alloc(sdev2) - attaches a freshly kmalloced struct to sdev2
slave_configure(sdev2) - inits sdev2->hostdata struct state
slave_destroy(sdev1) - destroys original struct, leaving the configured
struct untouched
In my driver I don't attempt to do anything like send cache flush commands
or the like, so I don't have the shutdown difficulties you do and things
work quite nicely.
We could make things work much nicer for your driver if Jens makes those
changes to the block layer that I just suggested (hint! hint!)
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
^ permalink raw reply
* [PATCH 2.5.52] : IrDA drivers quick module fixes
From: Jean Tourrilhes @ 2002-12-17 22:36 UTC (permalink / raw)
To: Jeff Garzik, Linux kernel mailing list; +Cc: Rusty Russell
Hi Jeff,
Here are the obvious fixes for some of the IrDA drivers to
make them happy in 2.5.52.
Have fun...
Jean
----------------------------------------------------------------
diff -u -p linux/include/net/irda/vlsi_ir.d0.h linux/include/net/irda/vlsi_ir.h
--- linux/include/net/irda/vlsi_ir.d0.h Tue Dec 10 14:28:13 2002
+++ linux/include/net/irda/vlsi_ir.h Tue Dec 10 14:28:33 2002
@@ -27,6 +27,7 @@
#ifndef IRDA_VLSI_FIR_H
#define IRDA_VLSI_FIR_H
+#include <linux/version.h>
#if LINUX_VERSION_CODE < KERNEL_VERSION(2,5,4)
#ifdef CONFIG_PROC_FS
/* PDE() introduced in 2.5.4 */
diff -u -p -r linux/drivers/net/irda.d0/ali-ircc.c linux/drivers/net/irda/ali-ircc.c
--- linux/drivers/net/irda.d0/ali-ircc.c Tue Dec 10 14:12:43 2002
+++ linux/drivers/net/irda/ali-ircc.c Tue Dec 17 12:03:13 2002
@@ -1303,6 +1303,9 @@ static int ali_ircc_net_init(struct net_
{
IRDA_DEBUG(2, "%s(), ---------------- Start ----------------\n", __FUNCTION__ );
+ /* Keep track of module usage */
+ SET_MODULE_OWNER(dev);
+
/* Setup to be a normal IrDA network device driver */
irda_device_setup(dev);
@@ -1369,8 +1372,6 @@ static int ali_ircc_net_open(struct net_
*/
self->irlap = irlap_open(dev, &self->qos, hwname);
- MOD_INC_USE_COUNT;
-
IRDA_DEBUG(2, "%s(), ----------------- End ------------------\n", __FUNCTION__ );
return 0;
@@ -1410,8 +1411,6 @@ static int ali_ircc_net_close(struct net
free_irq(self->io.irq, dev);
free_dma(self->io.dma);
-
- MOD_DEC_USE_COUNT;
IRDA_DEBUG(2, "%s(), ----------------- End ------------------\n", __FUNCTION__ );
diff -u -p -r linux/drivers/net/irda.d0/donauboe.c linux/drivers/net/irda/donauboe.c
--- linux/drivers/net/irda.d0/donauboe.c Tue Dec 10 14:10:45 2002
+++ linux/drivers/net/irda/donauboe.c Tue Dec 17 12:03:38 2002
@@ -1388,6 +1388,9 @@ toshoboe_net_init (struct net_device *de
{
IRDA_DEBUG (4, "%s()\n", __FUNCTION__);
+ /* Keep track of module usage */
+ SET_MODULE_OWNER(dev);
+
/* Setup to be a normal IrDA network device driver */
irda_device_setup (dev);
@@ -1435,8 +1438,6 @@ toshoboe_net_open (struct net_device *de
self->irdad = 1;
- MOD_INC_USE_COUNT;
-
return 0;
}
@@ -1466,8 +1467,6 @@ toshoboe_net_close (struct net_device *d
{
toshoboe_stopchip (self);
}
-
- MOD_DEC_USE_COUNT;
return 0;
}
diff -u -p -r linux/drivers/net/irda.d0/irda-usb.c linux/drivers/net/irda/irda-usb.c
--- linux/drivers/net/irda.d0/irda-usb.c Mon Dec 16 11:31:43 2002
+++ linux/drivers/net/irda/irda-usb.c Tue Dec 17 12:03:58 2002
@@ -904,6 +904,9 @@ static int irda_usb_net_init(struct net_
{
IRDA_DEBUG(1, "%s()\n", __FUNCTION__);
+ /* Keep track of module usage */
+ SET_MODULE_OWNER(dev);
+
/* Set up to be a normal IrDA network device driver */
irda_device_setup(dev);
@@ -974,7 +977,6 @@ static int irda_usb_net_open(struct net_
irda_usb_submit(self, NULL, self->rx_urb[i]);
/* Ready to play !!! */
- MOD_INC_USE_COUNT;
return 0;
}
@@ -1025,8 +1027,6 @@ static int irda_usb_net_close(struct net
if (self->irlap)
irlap_close(self->irlap);
self->irlap = NULL;
-
- MOD_DEC_USE_COUNT;
return 0;
}
diff -u -p -r linux/drivers/net/irda.d0/nsc-ircc.c linux/drivers/net/irda/nsc-ircc.c
--- linux/drivers/net/irda.d0/nsc-ircc.c Mon Nov 4 14:30:03 2002
+++ linux/drivers/net/irda/nsc-ircc.c Tue Dec 17 13:33:19 2002
@@ -1866,6 +1866,9 @@ static int nsc_ircc_net_init(struct net_
{
IRDA_DEBUG(4, "%s()\n", __FUNCTION__);
+ /* Keep track of module usage */
+ SET_MODULE_OWNER(dev);
+
/* Setup to be a normal IrDA network device driver */
irda_device_setup(dev);
@@ -1934,8 +1937,6 @@ static int nsc_ircc_net_open(struct net_
*/
self->irlap = irlap_open(dev, &self->qos, hwname);
- MOD_INC_USE_COUNT;
-
return 0;
}
@@ -1982,8 +1983,6 @@ static int nsc_ircc_net_close(struct net
/* Restore bank register */
outb(bank, iobase+BSR);
-
- MOD_DEC_USE_COUNT;
return 0;
}
diff -u -p -r linux/drivers/net/irda.d0/w83977af_ir.c linux/drivers/net/irda/w83977af_ir.c
--- linux/drivers/net/irda.d0/w83977af_ir.c Tue Dec 10 14:13:18 2002
+++ linux/drivers/net/irda/w83977af_ir.c Tue Dec 17 13:34:44 2002
@@ -1197,6 +1197,9 @@ static int w83977af_net_init(struct net_
{
IRDA_DEBUG(0, "%s()\n", __FUNCTION__ );
+ /* Keep track of module usage */
+ SET_MODULE_OWNER(dev);
+
/* Set up to be a normal IrDA network device driver */
irda_device_setup(dev);
@@ -1267,8 +1270,6 @@ static int w83977af_net_open(struct net_
*/
self->irlap = irlap_open(dev, &self->qos, hwname);
- MOD_INC_USE_COUNT;
-
return 0;
}
@@ -1316,8 +1317,6 @@ static int w83977af_net_close(struct net
/* Restore bank register */
outb(set, iobase+SSR);
-
- MOD_DEC_USE_COUNT;
return 0;
}
^ permalink raw reply
* 2.5.52 PNP failure
From: Richard A Nelson @ 2002-12-17 22:34 UTC (permalink / raw)
To: linux-kernel
Hand transcribed, so probably missing something important ...
Oops: 0000
Eip: 0060:[<c01cdbf3>] Not tainted
EIP is at compare_pnp_id+0x4f/0x78
Call Trace:
[<c01cfa43>] pnp_name_device+0x23/0x58
[<c01cd9af>] __pnp_add_device+0xf/0xc8
[<c01cdab4>] pnp_add_device+0x4c/0x54
[<c010509b>] init+0x33/0x188
[<c0105068>] init+0x0/0x188
[<c0109211>] kernel_thread_helper+0x5/0xc
<0>Kernel panic: Attempted to kill init!
--
Rick Nelson
I can saw a woman in two, but you won't want to look in the box when I do
'For My Next Trick I'll Need a Volunteer' -- Warren Zevon
^ permalink raw reply
* Re: PATCH
From: Greg Lindahl @ 2002-12-17 22:29 UTC (permalink / raw)
To: linux-mips
In-Reply-To: <1039841567.25391.13.camel@adsl.pacbell.net>
On Fri, Dec 13, 2002 at 08:52:47PM -0800, Pete Popov wrote:
> This patch was sent to the RageXL maintainer but I don't think he was
> interested in it. Others might find it useful on embedded systems. It
> initializes the RageXL card when there is no system bios to initialize
> it from the video bios. Tested on the Pb1500; makes a really good
> workstation.
Pete,
Is there a website with info about graphics cards on non-x86
architectures? Most cards require their own BIOS to be run at boot
time. This issue ought to be of interest to lots of other communities
than MIPS.
-- greg
^ permalink raw reply
* Re: 2.5.52 compile error
From: eric lin @ 2002-12-18 6:39 UTC (permalink / raw)
To: Bob Miller; +Cc: linux-kernel
In-Reply-To: <20021217211618.GB1069@doc.pdx.osdl.net>
Bob Miller wrote:
> On Tue, Dec 17, 2002 at 03:57:01PM -0500, rtilley wrote:
>
>>Using RH's default *i686.config to build a vanilla 2.5.52 kernel. It keeps
>>returning this error on 2 totally different x86 PCs:
>>
>>
>>drivers/built-in.o: In function `kd_nosound':
>>drivers/built-in.o(.text+0x1883f): undefined reference to `input_event'
>>drivers/built-in.o(.text+0x18861): undefined reference to `input_event'
>>drivers/built-in.o: In function `kd_mksound':
>>drivers/built-in.o(.text+0x1890a): undefined reference to `input_event'
>>drivers/built-in.o: In function `kbd_bh':
>>drivers/built-in.o(.text+0x197a2): undefined reference to `input_event'
>>drivers/built-in.o(.text+0x197c1): undefined reference to `input_event'
>>drivers/built-in.o(.text+0x197e0): more undefined references to `input_event'
>>follow
>>drivers/built-in.o: In function `kbd_connect':
>>drivers/built-in.o(.text+0x19d54): undefined reference to `input_open_device'
>>drivers/built-in.o: In function `kbd_disconnect':
>>drivers/built-in.o(.text+0x19d7f): undefined reference to `input_close_device'
>>drivers/built-in.o: In function `kbd_init':
>>drivers/built-in.o(.init.text+0x12c1): undefined reference to
>>`input_register_handler'
>>make: *** [.tmp_vmlinux1] Error 1
>>
>>
>>Where is the fix for this?
>>
>
> At your finger tips ;-). Turn on CONFIG_INPUT via "Input device support"
> off the main page.
I did not know what is that mean (off the man page)?
>
Is that at menuconfig
or
should modify any source code?
--
Sincere Eric
www.linuxspice.com
linux pc for sale
^ permalink raw reply
* [PATCH] (v3) move LOG_BUF_SIZE to header/config
From: Randy.Dunlap @ 2002-12-17 22:33 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
In-Reply-To: <3DFF5E67.C0BA874C@digeo.com>
Changes from yesterday:
a. use a shift value (suggested by HCH); probably still not as quite
as free and open as he suggested, but I had user-friendliness
problems with that.
b. allow a wider range of values (HCH and James Cloos):
smaller added, larger can be added as needed.
c. put common config into kernel/Kconfig and include that in each
arch/*/Kconfig
More comments?
--
~Randy
patch_name: logbuf-config-2552.patch
patch_version: 2002.12.17
author: Randy Dunlap <rddunlap@osdl.org>
description: change LOG_BUF_SIZE to a config option (LOG_BUF_SHIFT)
product: linux
product_versions: 2.5.52
changelog: (a) move to a common kernel/Kconfig;
(b) use a SHIFT value (enforces power of 2, gives more choices)
URL:
requires: kconfig in 2.5.52
conflicts:
diffstat:
arch/alpha/Kconfig | 2 +
arch/arm/Kconfig | 2 +
arch/cris/Kconfig | 2 +
arch/ia64/Kconfig | 3 ++
arch/m68k/Kconfig | 2 +
arch/m68knommu/Kconfig | 2 +
arch/mips/Kconfig | 2 +
arch/mips64/Kconfig | 2 +
arch/parisc/Kconfig | 2 +
arch/ppc/Kconfig | 2 +
arch/ppc64/Kconfig | 2 +
arch/s390/Kconfig | 2 +
arch/s390x/Kconfig | 2 +
arch/sh/Kconfig | 2 +
arch/sparc/Kconfig | 2 +
arch/sparc64/Kconfig | 2 +
arch/um/Kconfig | 2 +
arch/v850/Kconfig | 2 +
arch/x86_64/Kconfig | 2 +
kernel/Kconfig | 55 +++++++++++++++++++++++++++++++++++++++++++++++++
kernel/printk.c | 11 ---------
21 files changed, 95 insertions(+), 10 deletions(-)
--- ./arch/m68k/Kconfig%LOGBUF Sun Dec 15 18:08:11 2002
+++ ./arch/m68k/Kconfig Tue Dec 17 14:08:33 2002
@@ -2346,3 +2346,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/sparc/Kconfig%LOGBUF Sun Dec 15 18:07:42 2002
+++ ./arch/sparc/Kconfig Tue Dec 17 14:11:06 2002
@@ -1422,3 +1422,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/sparc64/Kconfig%LOGBUF Sun Dec 15 18:08:16 2002
+++ ./arch/sparc64/Kconfig Tue Dec 17 14:11:13 2002
@@ -1710,3 +1710,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/ppc/Kconfig%LOGBUF Sun Dec 15 18:08:23 2002
+++ ./arch/ppc/Kconfig Tue Dec 17 14:10:18 2002
@@ -1872,3 +1872,5 @@
source "crypto/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/m68knommu/Kconfig%LOGBUF Sun Dec 15 18:08:13 2002
+++ ./arch/m68knommu/Kconfig Tue Dec 17 14:08:52 2002
@@ -759,3 +759,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/alpha/Kconfig%LOGBUF Sun Dec 15 18:08:14 2002
+++ ./arch/alpha/Kconfig Tue Dec 17 14:07:34 2002
@@ -1030,3 +1030,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/cris/Kconfig%LOGBUF Sun Dec 15 18:08:19 2002
+++ ./arch/cris/Kconfig Tue Dec 17 14:08:06 2002
@@ -759,3 +759,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/mips/Kconfig%LOGBUF Sun Dec 15 18:07:56 2002
+++ ./arch/mips/Kconfig Tue Dec 17 14:08:59 2002
@@ -1284,3 +1284,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/x86_64/Kconfig%LOGBUF Sun Dec 15 18:08:14 2002
+++ ./arch/x86_64/Kconfig Tue Dec 17 14:11:54 2002
@@ -700,3 +700,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/ppc64/Kconfig%LOGBUF Sun Dec 15 18:08:09 2002
+++ ./arch/ppc64/Kconfig Tue Dec 17 14:10:25 2002
@@ -559,3 +559,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/um/Kconfig%LOGBUF Sun Dec 15 18:07:57 2002
+++ ./arch/um/Kconfig Tue Dec 17 14:11:35 2002
@@ -171,3 +171,5 @@
endmenu
+source "kernel/Kconfig"
+
--- ./arch/arm/Kconfig%LOGBUF Sun Dec 15 18:08:09 2002
+++ ./arch/arm/Kconfig Tue Dec 17 14:07:56 2002
@@ -1228,3 +1228,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/parisc/Kconfig%LOGBUF Sun Dec 15 18:08:11 2002
+++ ./arch/parisc/Kconfig Tue Dec 17 14:10:11 2002
@@ -423,3 +423,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/ia64/Kconfig%LOGBUF Sun Dec 15 18:08:21 2002
+++ ./arch/ia64/Kconfig Tue Dec 17 14:08:24 2002
@@ -891,3 +891,6 @@
source "security/Kconfig"
source "crypto/Kconfig"
+
+source "kernel/Kconfig"
+
--- ./arch/mips64/Kconfig%LOGBUF Sun Dec 15 18:07:52 2002
+++ ./arch/mips64/Kconfig Tue Dec 17 14:09:07 2002
@@ -727,3 +727,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/s390x/Kconfig%LOGBUF Sun Dec 15 18:07:59 2002
+++ ./arch/s390x/Kconfig Tue Dec 17 14:10:41 2002
@@ -346,3 +346,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/v850/Kconfig%LOGBUF Sun Dec 15 18:07:56 2002
+++ ./arch/v850/Kconfig Tue Dec 17 14:11:46 2002
@@ -452,4 +452,6 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
#############################################################################
--- ./arch/sh/Kconfig%LOGBUF Sun Dec 15 18:08:23 2002
+++ ./arch/sh/Kconfig Tue Dec 17 14:10:52 2002
@@ -1276,3 +1276,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./arch/s390/Kconfig%LOGBUF Sun Dec 15 18:07:54 2002
+++ ./arch/s390/Kconfig Tue Dec 17 14:10:33 2002
@@ -337,3 +337,5 @@
source "lib/Kconfig"
+source "kernel/Kconfig"
+
--- ./kernel/Kconfig%LOGBUF Tue Dec 17 14:00:31 2002
+++ ./kernel/Kconfig Tue Dec 17 14:16:36 2002
@@ -0,0 +1,55 @@
+# This general setup config file is read _after_ all other config files.
+# It is for generic kernel options that cannot be handled elsewhere,
+# including some generic options that are processor-dependent.
+# This is also _not_ for device driver options.
+# They should be handled in their driver subsystem areas.
+
+menu "Common kernel setup (more)"
+
+choice
+ prompt "Kernel log buffer size"
+ default LOG_BUF_SHIFT_17 if ARCH_S390
+ default LOG_BUF_SHIFT_16 if X86_NUMAQ || IA64
+ default LOG_BUF_SHIFT_15 if SMP
+ default LOG_BUF_SHIFT_14
+ help
+ Select kernel log buffer size from this list (power of 2).
+ Defaults: 17 (=> 128 KB for S/390)
+ 16 (=> 64 KB for x86 NUMAQ or IA-64)
+ 15 (=> 32 KB for SMP)
+ 14 (=> 16 KB for uniprocessor)
+
+config LOG_BUF_SHIFT_17
+ bool "128 KB"
+ default y if ARCH_S390
+
+config LOG_BUF_SHIFT_16
+ bool "64 KB"
+ default y if X86_NUMAQ || IA64
+
+config LOG_BUF_SHIFT_15
+ bool "32 KB"
+ default y if SMP
+
+config LOG_BUF_SHIFT_14
+ bool "16 KB"
+
+config LOG_BUF_SHIFT_13
+ bool "8 KB"
+
+config LOG_BUF_SHIFT_12
+ bool "4 KB"
+
+endchoice
+
+config LOG_BUF_SHIFT
+ int
+ default 17 if LOG_BUF_SHIFT_17=y
+ default 16 if LOG_BUF_SHIFT_16=y
+ default 15 if LOG_BUF_SHIFT_15=y
+ default 14 if LOG_BUF_SHIFT_14=y
+ default 13 if LOG_BUF_SHIFT_13=y
+ default 12 if LOG_BUF_SHIFT_12=y
+
+endmenu
+
--- ./kernel/printk.c%LOGBUF Sun Dec 15 18:08:24 2002
+++ ./kernel/printk.c Tue Dec 17 14:01:50 2002
@@ -30,16 +30,7 @@
#include <asm/uaccess.h>
-#if defined(CONFIG_X86_NUMAQ) || defined(CONFIG_IA64)
-#define LOG_BUF_LEN (65536)
-#elif defined(CONFIG_ARCH_S390)
-#define LOG_BUF_LEN (131072)
-#elif defined(CONFIG_SMP)
-#define LOG_BUF_LEN (32768)
-#else
-#define LOG_BUF_LEN (16384) /* This must be a power of two */
-#endif
-
+#define LOG_BUF_LEN (1 << CONFIG_LOG_BUF_SHIFT)
#define LOG_BUF_MASK (LOG_BUF_LEN-1)
#ifndef arch_consoles_callable
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.