* RE : DOC2k booting speed ...
From: Philippe @ 2004-01-26 16:15 UTC (permalink / raw)
To: linux-mtd
In-Reply-To: <1075129659.24024.86.camel@hades.cambridge.redhat.com>
Hi,
Thank you for your quick answer
> Grub's drivers are not particularly optimised. Why use an initrd rather
> loaded by the bootloader, rather than having the kernel itself access
> the device? That should be much faster, and wouldn't even need to whole
> device to be read at startup.
As I cannot use JFFS2 with the DOC, I use an initrd to put the whole system
in ramdrive without having the doc mounted.
I did it to avoid filesystem failures.
Is there another way to
1) boot from the DOC,
2) build up the OS filesystem
3) umount the DOC ? -> protect filesystem in case of unexpected powerdown
I saw many things about pivot_root but didn't found any simple example to
get started.
Thank you.
^ permalink raw reply
* Re: [PATCH] Fix _STA checking in acpi_bus_add
From: Bjorn Helgaas @ 2004-01-26 16:15 UTC (permalink / raw)
To: Len Brown; +Cc: ACPI Developers
In-Reply-To: <1074919407.14755.6.camel-D2Zvc0uNKG8@public.gmane.org>
On Friday 23 January 2004 9:43 pm, Len Brown wrote:
> Applied.
Thanks!
> ps. did you find this because you've got a system where the actual
> get_status failed, or the _STA returned !present and that was ignored?
Umm... let's see... the latter, I guess. I found this because
ia64 linux was complaining about some invalid ranges in _CRS on
the Intel Tiger box. It turned out that the ranges all had
_LEN==0, and we should have been ignoring them anyway.
But somebody from HP-UX noticed that we were complaining about
ranges on a bridge that should have been !present according to
the _STA.
Now that you've applied this, we have to resolve the next issue
I found while investigating this: the chipset config interface
(CBN/CSFF) is reported as _STA==0x8, i.e., "functioning, but not
present". We can't find anything in the spec on how to interpret
this.
The problem here is that since CBN/CSFF is !present, we won't
enumerate devices under them. Therefore, we will no longer find
the AGP bridge on Big Sur.
Bjorn
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
^ permalink raw reply
* [Bluez-users] rfcomm shouldn't fail silently
From: Edd Dumbill @ 2004-01-26 16:14 UTC (permalink / raw)
To: BlueZ Mailing List
As reported in this bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=229167
rfcomm shouldn't fail silently if an invalid command is given to ie.
-- Edd
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply
* [PATCH] EDD report URL change
From: Matt Domsch @ 2004-01-26 16:13 UTC (permalink / raw)
To: akpm, torvalds; +Cc: linux-kernel
Andrew, thanks for merging my changeset 1.1505 below into -rc1-mm2
already. I append a patch my changeset 1.1506 below, which changes
the EDD report URL to a new dell.com server.
Linus, please do a
bk pull http://mdomsch.bkbits.net/linux-2.5-edd-for-linus
This will update the following files:
Documentation/i386/zero-page.txt | 4 +++-
arch/i386/boot/setup.S | 21 +++++++++++++++++++++
arch/i386/kernel/edd.c | 26 +++++++++++++++++++++++---
arch/i386/kernel/i386_ksyms.c | 6 ------
arch/i386/kernel/setup.c | 7 +++++++
include/asm-i386/edd.h | 6 +++++-
include/asm-i386/setup.h | 1 +
7 files changed, 60 insertions, 11 deletions
through these ChangeSets:
<Matt_Domsch@dell.com> (04/01/26 1.1506)
EDD: change report URL, bump version
<Matt_Domsch@dell.com> (04/01/20 1.1505)
EDD: read disk80 MBR signature, export through edd module
There are 4 bytes in the MSDOS master boot record, at offset 0x1b8,
which may contain a per-system-unique signature. By first writing a
unique signature to each disk in the system, then rebooting, and then
reading the MBR to get the signature for the boot disk (int13 dev
80h), userspace may use it to compare against disks it knows as named
/dev/[hs]d[a-z], and thus determine which disk is the BIOS boot disk,
thus where the /boot, / and boot loaders should be placed.
This is useful in the case where the BIOS is not EDD3.0 compliant,
thus doesn't provide the PCI bus/dev/fn and IDE/SCSI location of the
boot disk, yet you need to know which disk is the boot disk. It's
most useful in OS installers.
This patch retrieves the signature from the disk in setup.S, stores it
in a space reserved in the empty_zero_page, copies it somewhere safe
in setup.c, and exports it via
/sys/firmware/edd/int13_disk80/mbr_signature in edd.c. Code is
covered under CONFIG_EDD=[ym].
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
You can import this changeset into BK by piping this whole message to
'| bk receive [path to repository]' or apply the patch as usual.
===================================================================
ChangeSet@1.1506, 2004-01-26 09:54:48-06:00, Matt_Domsch@dell.com
EDD: change report URL, bump version
edd.c | 4 ++--
1 files changed, 2 insertions, 2 deletions
diff -Nru a/arch/i386/kernel/edd.c b/arch/i386/kernel/edd.c
--- a/arch/i386/kernel/edd.c Mon Jan 26 10:03:36 2004
+++ b/arch/i386/kernel/edd.c Mon Jan 26 10:03:36 2004
@@ -60,9 +60,9 @@
MODULE_DESCRIPTION("sysfs interface to BIOS EDD information");
MODULE_LICENSE("GPL");
-#define EDD_VERSION "0.11 2003-Dec-17"
+#define EDD_VERSION "0.12 2004-Jan-26"
#define EDD_DEVICE_NAME_SIZE 16
-#define REPORT_URL "http://domsch.com/linux/edd30/results.html"
+#define REPORT_URL "http://linux.dell.com/edd/results.html"
#define left (PAGE_SIZE - (p - buf) - 1)
===================================================================
This BitKeeper patch contains the following changesets:
1.1506
## Wrapped with gzip_uu ##
M'XL( %@Z%4 \64VV[30!"&K[-/,4HNP?;L.;$45&@B:"DT<@DW"$4;>X.C
M^!#9FP*2'Q[;I0=0*2JJA&U9]FAF-/^_GV8$R]I6X>"=<6XU*_,Z3LD(WI2U
M"P>)S3(_+O,V$)5E&PC2,K=!GO1IP7H7V"0)LFUQ^.8Q7WKMG[<I*Z^+U*2M
M6A@7IW!IJSH<4)_?1-SWO0T'T?SU\NQE1,AT"L>I*;[8"^M@.B6NK"Y-EM1'
MQJ596?BN,D6=6V>Z89J;U(8ALO:65'.4JJ$*A6YBFE!J!+4),C%6@MQ1=G2M
MZ--/#9]_[2:0M@VID%PUBJ)",@/J4XD*4 1( ]9^3$(I0C'V4(6(<%]W>$;!
M0_(*GE;(,8EA/IN%$/>%4-E]63E81F?/87W(][W1V[(@;T$A%9HL;FTEWB,O
M0M @>7&OOL94[?%O^5@%.UL5-NLX\.->!D6<,*1<BH9*ID4S46JB-QN]-@G?
M:!,_MF-W)HI**;AH&--:][S<G]_!\^0#_P6@AR?O:!)<-HSCF/<T,?R=)2X>
M9(F!Q_XG2U>FGX-7?>V?EHW%'_S_!\IFB@,E)_U[E-C-MK#=8*N/\^CBY/P]
M#-&G##HWO5-3>$P-VQ+9E\@[)=%\<1Y]6+7SPS!U;A\&5WO)O_:Q7U65K0^9
?J_W4Y=GP=D'%J8UW]2&?QE9KJ=>,_ #0G52T%@4
^ permalink raw reply
* Re: NFSv4 & /etc/exportfs
From: Vincent ROQUETA @ 2004-01-26 16:13 UTC (permalink / raw)
To: J. Bruce Fields; +Cc: nfs
In-Reply-To: <20040126152747.GA14181@fieldses.org>
Le Lundi 26 Janvier 2004 16:27, J. Bruce Fields a =E9crit :
> On Mon, Jan 26, 2004 at 03:44:07PM +0100, Vincent ROQUETA wrote:
> > I tried to mount a directory using the old nfs conf. format (as indicat=
ed
> > in the man) and using the new one, as described here :
> > http://www.citi.umich.edu/projects/nfsv4/june_2002_rel/exports.html
>
> That's very out of date; the format described there was for a much older
> version of the code and will probably never be used. See
> http://www.citi.umich.edu/projects/nfsv4/linux/ for instructions on
> exporting to nfsv4. The idea is to use the fsid=3D0 option to mark one
> export as the nfsv4 "pseudofilesystem root" (the filesystem clients will
> get if they mount yourserver:/) and then attach other exports underneath
> it using mount --bind.
>
> --Bruce Fields
Great! It works fine ;)=20
Thx
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply
* Re: [parisc-linux] help installation failed on C240 (fx4) workstation
From: Grant Grundler @ 2004-01-26 16:13 UTC (permalink / raw)
To: Reinhold Flecke CCF; +Cc: parisc-linux
In-Reply-To: <LBEMKLBEFDGDOGGAOGIKOEJPCCAA.reinhold.flecke@ccf-consulting.de>
On Mon, Jan 26, 2004 at 12:13:22PM +0100, Reinhold Flecke CCF wrote:
> I downloaded the "debian-30r2-hppa-binary-1.iso" and burned it to CD.
> If I start the installation on my C240 (fx4) workstation with the command:
> bo sescsi.2.0
FX-4 graphics is not supported.
Either use serial console or replace the FX4 with PCI FX-E.
sorry,
grant
^ permalink raw reply
* [Ocfs2-devel] Problems building OCFS2
From: Villalovos, John L @ 2004-01-26 16:12 UTC (permalink / raw)
To: ocfs2-devel
I noticed that OCFS2 got updated in the last few days.
I just tried to do a build and got this:
[root@linuxjohn2 trunk]# make
make -C src
make[1]: Entering directory `/root/ocfs2/trunk/src'
make[1]: *** No rule to make target `inc/io.h', needed by `alloc.c'.
Stop.
make[1]: Leaving directory `/root/ocfs2/trunk/src'
make: *** [src] Error 2
[root@linuxjohn2 trunk]#
I can not find the io.h file that the Makefile specifies.
Thanks,
John
^ permalink raw reply
* Xastir.
From: Erik Jakobsen @ 2004-01-26 16:10 UTC (permalink / raw)
To: linux-hams
Hi.
I'm running Xastir on my SuSE Linux 8.2. Is there any here on the list,
that have maps for Europe and Scandinavian ?.
--
Med venlig hilsen - Best regards.
Erik Jakobsen - eja@urbakken.dk.
Licensed radioamateur with the callsign OZ4KK.
SuSE Linux 8.2 Proff.
Registered as user #319488 with the Linux Counter, http://counter.li.org.
^ permalink raw reply
* Re: [Kernel-janitors] [PATCH] Fix warning in drivers/ide/pci/triflex.c
From: Felipe W Damasio @ 2004-01-26 16:06 UTC (permalink / raw)
To: kernel-janitors
In-Reply-To: <1074874158.5269.3.camel@telecentrolivre>
Greetings,
Luiz Fernando Capitulino wrote:
> hi all,
>
> this patch fixes this warning:
>
> drivers/ide/pci/triflex.c:49: warning: `triflex_get_info' defined but not used
>
> here is:
>
> diff -X dontdiff -Nru linux-2.6.2-rc2/drivers/ide/pci/triflex.c linux-2.6.2-rc2~/drivers/ide/pci/triflex.c
> --- linux-2.6.2-rc2/drivers/ide/pci/triflex.c 2003-10-08 16:24:04.000000000 -0300
> +++ linux-2.6.2-rc2~/drivers/ide/pci/triflex.c 2004-01-26 11:02:33.000000000 -0200
> @@ -45,6 +45,7 @@
>
> static struct pci_dev *triflex_dev;
>
> +#ifdef CONFIG_PROC_FS
> static int triflex_get_info(char *buf, char **addr, off_t offset, int count)
> {
> char *p = buf;
> @@ -91,6 +92,7 @@
>
> return len > count ? count : len;
> }
> +#endif
Do we really need this chunk?
> static int triflex_tune_chipset(ide_drive_t *drive, u8 xferspeed)
> {
> diff -X dontdiff -Nru linux-2.6.2-rc2/drivers/ide/pci/triflex.h linux-2.6.2-rc2~/drivers/ide/pci/triflex.h
> --- linux-2.6.2-rc2/drivers/ide/pci/triflex.h 2003-10-08 16:24:26.000000000 -0300
> +++ linux-2.6.2-rc2~/drivers/ide/pci/triflex.h 2004-01-26 11:02:33.000000000 -0200
> @@ -14,8 +14,16 @@
>
> static unsigned int __devinit init_chipset_triflex(struct pci_dev *, const char *);
> static void init_hwif_triflex(ide_hwif_t *);
> +#ifdef CONFIG_PROC_FS
> static int triflex_get_info(char *, char **, off_t, int);
.
.
.
> +#endif
Since triflex_get_info is already #ifdef'd out if CONFIG_PROC_FS is not
set, we don't need to put that extra #ifdef on the .c file, since that
function will not get used anyway.
IIRC the policy for adding #ifdefs on .c files is when it's really
necessary, and I don't really see the point for this (expect object size
and an extra symbol defined, which I don't think it really hurts here).
Cheers,
Felipe
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
^ permalink raw reply
* Oops in kobject_put during rsync backup on 2.6.2-rc1-mm3
From: Walt H @ 2004-01-26 16:03 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 368 bytes --]
Hello,
I've received a couple of oopses while doing an rsync backup on
2.6.2-rc1 with mm1-mm3 patchsets. I've since backed out the
sysfs-pin-kobject.patch and it succeeds in the rsync. I've captured the
oops, but no longer have the running kernel which exhibited it, so not
sure how helpful the decoded oops will be. System is a 2xAMD MP system
w/ 1 GB ram.
-Walt
[-- Attachment #2: decodedoops.txt --]
[-- Type: text/plain, Size: 5302 bytes --]
ksymoops 2.4.9 on i686 2.6.2-rc1-mm3. Options used
-V (specified)
-K (specified)
-l /proc/modules (default)
-o /lib/modules/2.6.2-rc1-mm3/ (default)
-m /boot/System.map-2.6.2-rc1-mm3.old (specified)
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Unable to handle kernel paging request at virtual address f9a4476c
c01b92e2
*pde = 01bbf067
Oops: 0002 [#1]
CPU: 1
EIP: 0060:[<c01b92e2>] Tainted: PF VLI
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010282
eax: f9a44754 ebx: f685d1c0 ecx: f685d1d8 edx: f9a44754
esi: f698d180 edi: f685d1c0 ebp: 0000006b esp: c1b8be60
ds: 007b es: 007b ss: 0068
Stack: c018a0a4 f9a44754 c1b8a000 c016b4bf f698d180 f685d1c0 f637bb00 f672ec00
f672ec00 c016ba37 f637bb00 00000080 000000d0 000001c1 f7ffe560 c016bf79
00000080 c0145270 00000080 000000d0 0bf7a890 00000000 00000441 00000000
Call Trace:
[<c018a0a4>] sysfs_d_iput+0x16/0x21
[<c016b4bf>] dput+0x1eb/0x241
[<c016ba37>] prune_dcache+0x1e7/0x236
[<c016bf79>] shrink_dcache_memory+0x15/0x1c
[<c0145270>] shrink_slab+0xfc/0x14c
[<c0146630>] balance_pgdat+0x13f/0x1ff
[<c01467f8>] kswapd+0x108/0x10d
[<c0122be0>] autoremove_wake_function+0x0/0x36
[<c028d9da>] ret_from_fork+0x6/0x14
[<c0122be0>] autoremove_wake_function+0x0/0x36
[<c01466f0>] kswapd+0x0/0x10d
[<c010b1fd>] kernel_thread_helper+0x5/0xb
Code: ff 16 58 85 ff 74 0a 8d 47 10 50 e8 17 00 00 00 58 85 ed 74 0d 89 6c 24 14 5b 5e 5f 5d e9 05 00 00 00 5b 5e 5f 5d c3 8b 54 24 04 <f0> ff 4a 18 0f 94 c0 84 c0 74 09 89 54 24 04 e9 83 ff ff ff c3
>>EIP; c01b92e2 <kobject_put+4/19> <=====
>>eax; f9a44754 <_end+3962b10c/3fbe39b8>
>>ebx; f685d1c0 <_end+36443b78/3fbe39b8>
>>ecx; f685d1d8 <_end+36443b90/3fbe39b8>
>>edx; f9a44754 <_end+3962b10c/3fbe39b8>
>>esi; f698d180 <_end+36573b38/3fbe39b8>
>>edi; f685d1c0 <_end+36443b78/3fbe39b8>
>>esp; c1b8be60 <_end+1772818/3fbe39b8>
Trace; c018a0a4 <sysfs_d_iput+16/21>
Trace; c016b4bf <dput+1eb/241>
Trace; c016ba37 <prune_dcache+1e7/236>
Trace; c016bf79 <shrink_dcache_memory+15/1c>
Trace; c0145270 <shrink_slab+fc/14c>
Trace; c0146630 <balance_pgdat+13f/1ff>
Trace; c01467f8 <kswapd+108/10d>
Trace; c0122be0 <autoremove_wake_function+0/36>
Trace; c028d9da <ret_from_fork+6/14>
Trace; c0122be0 <autoremove_wake_function+0/36>
Trace; c01466f0 <kswapd+0/10d>
Trace; c010b1fd <kernel_thread_helper+5/b>
This architecture has variable length instructions, decoding before eip
is unreliable, take these instructions with a pinch of salt.
Code; c01b92b7 <kobject_cleanup+3e/65>
00000000 <_EIP>:
Code; c01b92b7 <kobject_cleanup+3e/65>
0: ff 16 call *(%esi)
Code; c01b92b9 <kobject_cleanup+40/65>
2: 58 pop %eax
Code; c01b92ba <kobject_cleanup+41/65>
3: 85 ff test %edi,%edi
Code; c01b92bc <kobject_cleanup+43/65>
5: 74 0a je 11 <_EIP+0x11>
Code; c01b92be <kobject_cleanup+45/65>
7: 8d 47 10 lea 0x10(%edi),%eax
Code; c01b92c1 <kobject_cleanup+48/65>
a: 50 push %eax
Code; c01b92c2 <kobject_cleanup+49/65>
b: e8 17 00 00 00 call 27 <_EIP+0x27>
Code; c01b92c7 <kobject_cleanup+4e/65>
10: 58 pop %eax
Code; c01b92c8 <kobject_cleanup+4f/65>
11: 85 ed test %ebp,%ebp
Code; c01b92ca <kobject_cleanup+51/65>
13: 74 0d je 22 <_EIP+0x22>
Code; c01b92cc <kobject_cleanup+53/65>
15: 89 6c 24 14 mov %ebp,0x14(%esp,1)
Code; c01b92d0 <kobject_cleanup+57/65>
19: 5b pop %ebx
Code; c01b92d1 <kobject_cleanup+58/65>
1a: 5e pop %esi
Code; c01b92d2 <kobject_cleanup+59/65>
1b: 5f pop %edi
Code; c01b92d3 <kobject_cleanup+5a/65>
1c: 5d pop %ebp
Code; c01b92d4 <kobject_cleanup+5b/65>
1d: e9 05 00 00 00 jmp 27 <_EIP+0x27>
Code; c01b92d9 <kobject_cleanup+60/65>
22: 5b pop %ebx
Code; c01b92da <kobject_cleanup+61/65>
23: 5e pop %esi
Code; c01b92db <kobject_cleanup+62/65>
24: 5f pop %edi
Code; c01b92dc <kobject_cleanup+63/65>
25: 5d pop %ebp
Code; c01b92dd <kobject_cleanup+64/65>
26: c3 ret
Code; c01b92de <kobject_put+0/19>
27: 8b 54 24 04 mov 0x4(%esp,1),%edx
This decode from eip onwards should be reliable
Code; c01b92e2 <kobject_put+4/19>
00000000 <_EIP>:
Code; c01b92e2 <kobject_put+4/19> <=====
0: f0 ff 4a 18 lock decl 0x18(%edx) <=====
Code; c01b92e6 <kobject_put+8/19>
4: 0f 94 c0 sete %al
Code; c01b92e9 <kobject_put+b/19>
7: 84 c0 test %al,%al
Code; c01b92eb <kobject_put+d/19>
9: 74 09 je 14 <_EIP+0x14>
Code; c01b92ed <kobject_put+f/19>
b: 89 54 24 04 mov %edx,0x4(%esp,1)
Code; c01b92f1 <kobject_put+13/19>
f: e9 83 ff ff ff jmp ffffff97 <_EIP+0xffffff97>
Code; c01b92f6 <kobject_put+18/19>
14: c3 ret
[-- Attachment #3: .config --]
[-- Type: text/plain, Size: 27923 bytes --]
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_STANDALONE=y
#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=19
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_EMBEDDED=y
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
#
# Processor support
#
#
# Select all processors your kernel should support
#
# CONFIG_CPU_386 is not set
# CONFIG_CPU_486 is not set
# CONFIG_CPU_586 is not set
# CONFIG_CPU_586TSC is not set
# CONFIG_CPU_586MMX is not set
# CONFIG_CPU_686 is not set
# CONFIG_CPU_PENTIUMII is not set
# CONFIG_CPU_PENTIUMIII is not set
# CONFIG_CPU_PENTIUMM is not set
# CONFIG_CPU_PENTIUM4 is not set
# CONFIG_CPU_K6 is not set
CONFIG_CPU_K7=y
# CONFIG_CPU_K8 is not set
# CONFIG_CPU_CRUSOE is not set
# CONFIG_CPU_WINCHIPC6 is not set
# CONFIG_CPU_WINCHIP2 is not set
# CONFIG_CPU_WINCHIP3D is not set
# CONFIG_CPU_CYRIXIII is not set
# CONFIG_CPU_VIAC3_2 is not set
CONFIG_CPU_ONLY_K7=y
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_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
# CONFIG_X86_4G is not set
# CONFIG_X86_SWITCH_PAGETABLES is not set
# CONFIG_X86_4G_VM_LAYOUT is not set
# CONFIG_X86_UACCESS_INDIRECT is not set
# CONFIG_X86_HIGH_ENTRY is not set
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_SMP=y
CONFIG_NR_CPUS=2
# CONFIG_SCHED_SMT is not set
CONFIG_PREEMPT=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=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 is not set
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
# CONFIG_EDD is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
CONFIG_HIGHPTE=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_SOFTWARE_SUSPEND is not set
# CONFIG_PM_DISK is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=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_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_RELAXED_AML is not set
# CONFIG_X86_PM_TIMER is not set
#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set
#
# CPU Frequency scaling
#
# 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_PCI_USE_VECTOR is not set
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_HOTPLUG=y
#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=m
#
# Device Drivers
#
#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# 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=y
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=10000
CONFIG_BLK_DEV_INITRD=y
# CONFIG_LBD is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
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_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_OFFBOARD=y
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 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_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
CONFIG_PDC202XX_FORCE=y
# 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 is not set
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_IVB=y
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_MAX_SD_DISKS=256
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_REPORT_LUNS=y
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX_CONFIG=m
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA23XX is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
# CONFIG_MD_LINEAR is not set
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_RAID6 is not set
CONFIG_MD_MULTIPATH=y
CONFIG_BLK_DEV_DM=m
CONFIG_DM_IOCTL_V4=y
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
CONFIG_IEEE1394=m
#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set
#
# Device Drivers
#
# CONFIG_IEEE1394_PCILYNX is not set
CONFIG_IEEE1394_OHCI1394=m
#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
CONFIG_IEEE1394_SBP2_PHYS_DMA=y
CONFIG_IEEE1394_ETH1394=m
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_CMP=m
CONFIG_IEEE1394_AMDTP=m
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Macintosh device drivers
#
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_NETLINK_DEV=m
CONFIG_UNIX=y
CONFIG_NET_KEY=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
# CONFIG_IP_MULTIPLE_TABLES is not set
# CONFIG_IP_ROUTE_MULTIPATH is not set
# CONFIG_IP_ROUTE_TOS is not set
# CONFIG_IP_ROUTE_VERBOSE is not set
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
# CONFIG_NET_IPGRE_BROADCAST 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=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_AMANDA=m
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=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_RECENT=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_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=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_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
# CONFIG_IP_NF_NAT_LOCAL is not set
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_NAT_AMANDA=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_CLASSIFY=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_ARP_MANGLE=m
CONFIG_IP_NF_COMPAT_IPCHAINS=m
CONFIG_IP_NF_COMPAT_IPFWADM=m
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK 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 is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
CONFIG_BONDING=m
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m
# CONFIG_ETHERTAP is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM 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_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
CONFIG_EEPRO100=m
# CONFIG_EEPRO100_PIO is not set
CONFIG_E100=m
# CONFIG_E100_NAPI 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 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
#
# 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_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PPP=m
# CONFIG_PPP_MULTILINK is not set
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE_MPPC=m
CONFIG_PPPOE=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
# CONFIG_SLIP_MODE_SLIP6 is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set
#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set
#
# Bluetooth support
#
# CONFIG_BT is not set
# CONFIG_KGDBOE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
# CONFIG_NET_POLL_CONTROLLER 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=y
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=y
# 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
# CONFIG_SERIO_PCIPS2 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 is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_UINPUT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=m
CONFIG_SERIAL_8250_ACPI=y
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=m
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=y
CONFIG_NVRAM=y
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_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
CONFIG_AGP_AMD=m
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=256
# CONFIG_HANGCHECK_TIMER is not set
#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m
#
# I2C Algorithms
#
# CONFIG_I2C_ALGOBIT is not set
# CONFIG_I2C_ALGOPCF is not set
#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI15X3 is not set
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD8111=m
# CONFIG_I2C_ELV is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_ISA is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VELLEMAN is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
#
# I2C Hardware Sensors Chip support
#
CONFIG_I2C_SENSOR=m
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ASB100 is not set
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_IT87=m
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set
#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
#
# Sound
#
CONFIG_SOUND=y
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
# 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=m
#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
CONFIG_SND_EMU10K1=m
# 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 is not set
# 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_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set
#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_UHCI_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_HP8200e=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
#
# 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_THRUSTMASTER_FF is not set
CONFIG_USB_HIDDEV=y
#
# USB HID Boot Protocol drivers
#
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_XPAD is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set
#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
#
# Video4Linux support is needed for USB Multimedia device support
#
#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
#
# USB port drivers
#
#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OMNINET is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GADGET is not set
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
# CONFIG_XFS_RT is not set
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_QUOTA=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=m
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
CONFIG_UDF_FS=m
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_RAMFS=y
#
# Miscellaneous filesystems
#
# 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_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V4 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_SUNRPC=m
# CONFIG_SUNRPC_GSS is not set
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
CONFIG_CIFS=m
# CONFIG_NCP_FS is not set
CONFIG_CODA_FS=m
# CONFIG_CODA_FS_OLD_API is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
# 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=m
# 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
#
# 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_DEBUG_PAGEALLOC is not set
# CONFIG_SPINLINE is not set
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_LOCKMETER is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_KGDB is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
#
# Security options
#
# CONFIG_SECURITY is not set
#
# 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_SHA512=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_TEST=m
#
# Library routines
#
CONFIG_CRC32=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
^ permalink raw reply
* 2.6.1: Alsa 0.9.7?
From: Harald Dunkel @ 2004-01-26 15:56 UTC (permalink / raw)
To: linux-kernel
Hi folks,
CONFIG_SND_VERSION says that Alsa in 2.6.1 is version
0.9.7. Is this correct?
I'm just curious.
Regards
Harri
^ permalink raw reply
* Re: Patch to fix Pax/Grsecurity Problems
From: Takashi Iwai @ 2004-01-26 15:58 UTC (permalink / raw)
To: Clemens Ladisch; +Cc: siti_veni, alsa-devel
In-Reply-To: <Pine.HPX.4.33n.0401261439360.24795-100000@studcom.urz.uni-halle.de>
At Mon, 26 Jan 2004 14:45:49 +0100 (MET),
Clemens Ladisch wrote:
>
> Takashi Iwai wrote:
> > Stephen Cook wrote:
> > >
> > > >> - qsort(hctl->pelems, hctl->count, sizeof(*hctl->pelems), compar);
> > > >> +
> > > >> + pthread_mutex_lock(&sync_lock);
> > > >> + compare_hctl = hctl;
> > > >> + qsort(hctl->pelems, hctl->count, sizeof(*hctl->pelems), hctl_compare);
> > > >> + pthread_mutex_unlock(&sync_lock);
> > >
> > > I hope I don't sound to persistent but I am just wondering when this
> > > patch is going to be merged or if there is anything I can do to help
> > > speed it up. Such as any changes to the patch etc.
> >
> > well, i'm also waiting for the response from others.
>
> Looks fine.
>
> We're already dependent on pthreads, and qsort doesn't pass extra
> parameters, so I don't see any better way to do this.
> ("Let's write our own sorting routine" is not better IMNSHO.)
agreed. it's on cvs now.
(will be included in 1.0.2 release.)
thanks,
Takashi
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
^ permalink raw reply
* FW: questions about production use
From: Williamson, Mark A @ 2004-01-26 15:58 UTC (permalink / raw)
To: xen-devel
Whoops ;-) - here's the reply I sent to Nick's e-mail. Accidentally
forgot to send it to the list as well...
>> [me talking about virtual disks]
>
> Sort of like LVM but run by Xen? Tha sounds very interesting.
Yes, it is rather like LVM. The user space virtual disk tools manage
allocation of disk extents and keep track of which extents belong to
which virtual disks. Then when you create the Virtual Block Device that
domains will use to access that virtual disk, Xen does all the address
translation, so it just appears like another other Xen block device to
the guest OS.
>> [me talking about the free pool]
>
> That sounds like just the job. We'd also want to be able to access
> all the virtual disks from Domain0 for administrative purposes (backup
> / transfer to a new host etc) but I guess that is possible.
Xen 1.2 and above have "automatic plumbing" of virtual block devices:
you create a virtual block device for a domain and it "just knows" that
it's there, a bit like hot plugging. You can use this to add a virtual
disk to a device node in dom0, do stuff with it, then remove it from
dom0 again. However, it is not safe to have two writers to one
filesystem (unless the filesystem explicitly supports it, which most
don't) and even with one reader and one writer, it's probably not a good
idea - you'll have to take virtual disks offline (by at least unmounting
them in the domain that's using them) before accessing them from dom0.
I expect you'd gathered this, though...
>> [me talking about re-exporting devices from dom0]
>
> Excellent!
>
> How much of this and the above is implemented now? Should I be
> checking out Xen 1.2 and reading the docs?
Virtual Disks are in the 1.2 and unstable trees right now. There was an
implementation of virtual disks in versions 1.0 and 1.1 but the rewrite
adds support for the new Python-based toolchain and some new features.
AFAIK nobody has used the new VD tools "in anger" yet but it's been
working pretty solidly in testing. At some stage after we've got 1.2
released (which will be soon) I'll be adding some more whizzy features
to the unstable tree but these would probably be backwards compatible
with 1.2.
The virtual disk howto is now slightly out of date but I will be
updating it presently. If you get stuck, there's always interactive
help on the mailing list ;-) - I can feed back any discussions we have
to make the docs better.
The ability to re-export devices from one domain that just appear like
an ordinary Xen block device to another domain is still at the design
stage, as yet. However, this is fairly high on the priority list at the
moment...
HTH,
Mark
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
^ permalink raw reply
* Re: 2.4.23 IDE hang on boot with two single-channel controllers
From: Jeremy Jackson @ 2004-01-26 15:56 UTC (permalink / raw)
To: Torben Mathiasen, linux-kernel, linux-ide
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
Hi,
(watch crossposting when replying all)
I'm hoping to reach the maintainer of the Linux IDE driver for the
Compaq TriFlex controller. I have a problem with this driver when used
with a Compaq Armada 7730MT while docked in the base station.
The driver appears to only support one triflex controller, due to a
missing check (that other chipset drivers have) that should prevent it
from registering a /proc interface more than once. The result is that
it hangs on boot in proc_ide_create() in an infinite loop.
triflex.c:
static unsigned int __init init_chipset_triflex(struct pci_dev *dev,
const char *name)
{
#ifdef CONFIG_PROC_FS
ide_pci_register_host_proc(&triflex_proc);
#endif
return 0;
}
It also appears that triflex_get_info() doesn't support more that one
controller.
I won't go into more detail until I can establish who might care :)
Regards,
Jeremy Jackson
[-- Attachment #2: 2.4.23 IDE hang on boot with two single-channel controllers --]
[-- Type: message/rfc822, Size: 3291 bytes --]
From: Jeremy Jackson <jerj@coplanar.net>
To: linux-ide@vger.kernel.org
Subject: 2.4.23 IDE hang on boot with two single-channel controllers
Date: Mon, 26 Jan 2004 09:44:49 -0500
Message-ID: <401527E1.6040108@coplanar.net>
Hi All,
Already posted this to linux-kernel.
kdb shows proc_ide_create() stuck in a loop when booting on a Compaq
Armada 7730MT while attached to the docking station.
This is a unique IDE hardware setup. Channel ide0's controller is in
the laptop, while ide1 is a separate controller (pci device) in the
docking station and is not always present.
This seems to be triggering a bug in ide-proc.c:
void proc_ide_create(void)
{
#ifdef CONFIG_BLK_DEV_IDEPCI
ide_pci_host_proc_t *p = ide_pci_host_proc_list;
#endif /* CONFIG_BLK_DEV_IDEPCI */
proc_ide_root = proc_mkdir("ide", 0);
if (!proc_ide_root) return;
create_proc_ide_interfaces();
create_proc_read_entry("drivers", 0, proc_ide_root,
proc_ide_read_drivers, NULL);
#ifdef CONFIG_BLK_DEV_IDEPCI
while (p != NULL) <------------------- INFINITE LOOP HERE
{
if (p->name != NULL && p->set == 1 && p->get_info != NULL)
{
p->parent = proc_ide_root;
create_proc_info_entry(p->name, 0, p->parent,
p->get_info);
p->set = 2;
}
p = p->next;
}
#endif /* CONFIG_BLK_DEV_IDEPCI */
}
I'm not sure if the problem is in the loop or bad data being setup
before it starts.
Assistance fixing it would be appreciated.
Regards,
Jeremy Jackson
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply
* button events will be not recognised (Dell I1100, A26 - kernel 2.6.1)
From: Nick Teen @ 2004-01-26 15:57 UTC (permalink / raw)
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
Hello folks!
Since a bios upgrade of my Dell Inspiron 1100 the ACPI
button event support is broken. acpid receives no
events and `cat /proc/acpi/event` gives no output
whatever I do.
(press the different buttons)
Can anybody help me out with a fixed dsdt table or
give me a hint how to correct them? i don´t know
exactly what i must change and if i recompile it i get
a lot of syntax errors.
Thanks a lot!!
Regards,
Nick
__________________________________________________________________
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Mit Yahoo! Suche finden Sie alles: http://suche.yahoo.de
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
^ permalink raw reply
* Re: New linux box
From: Ken Moffat @ 2004-01-26 15:57 UTC (permalink / raw)
To: S. Barret Dolph; +Cc: linux-newbie
In-Reply-To: <200401262213.43388.wheds8@ms66.hinet.net>
On Mon, 26 Jan 2004, S. Barret Dolph wrote:
> Well, my problems have much to do with hardware and it is time to get a new
> box. My old box ran for 6 years with Mandrake and never crashed. (X-windows
> crashed when setting up Matrox 450 though.) My question is what hardware is
> good to avoid. I only use my computer for work, no games, but I am on it at
> least 6 hours or more a day. I care mostly about stability and don't really
> care too much about speed. So more to the point are any of you aware of
> hardware that is a nightmare to install. Or a site which can help.
>
> Cordially,
> S. Barret Dolph
> Taipei Taiwan
> -
If it's that old, your biggest problem on anything new might be noise!
For stability with an Athlon or P4, don't skimp on the power supply. If
you don't need a lot of power, maybe something based on a via C3 might do
- but make sure you install i586 or i386 binaries, gcc usually thinks
C3s are i686 but they don't have the 'cmov' instruction.
Ken
--
This is a job for Riviera Kid!
-
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: [parisc-linux] kernel BUG at mm/shmem.c:585!
From: Grant Grundler @ 2004-01-26 15:53 UTC (permalink / raw)
To: John David Anglin; +Cc: Carlos O'Donell, parisc-linux
In-Reply-To: <200401260235.i0Q2Z783024373@hiauly1.hia.nrc.ca>
On Sun, Jan 25, 2004 at 09:35:07PM -0500, John David Anglin wrote:
> Is this on a SMP kernel (i.e., could this be a locking issue)?
no. I don't build or run SMP kernels on anything at the moment.
thanks,
grant
^ permalink raw reply
* RE: [LARTC] IMQ Stability
From: Michael S. Kazmier @ 2004-01-26 15:53 UTC (permalink / raw)
To: lartc
In-Reply-To: <marc-lartc-105066408632475@msgid-missing>
Hello Alex,
Perhaps I missed something below which ties eth0 and eth1 to the PPP pipe,
or its just my unfamiliarity with PPP.
Regardless, an interesting methodology. Do you think you could do the
following:
<eth0>----<ppp0>----<standard linux bridging / routing>---<ppp1>---<eth1>
The reason I ask is that I would like to, at the PPP level, apply CBQ or HTB
rate shaping to my each end user (ie, limit traffic to 256K or something
like that). And then, after each customer has their rate shaping, at the
ETH level I would like to priorize traffic (ie, all www prio 3, ssh -
telnet, prio 1, ftp prio 4, everything else prio 7)
Thoughts?
-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl] On
Behalf Of Alexander Clouter
Sent: Saturday, January 24, 2004 7:05 PM
To: lartc@mailman.ds9a.nl
Subject: Re: [LARTC] IMQ Stability
On Jan 24, mkazmier@sofast.net wrote:
> Thank you for the detailed discussion. There is no doubt that there is a
> need for an IMQ type device/funtionality. What would work really great,
> IMHO, is a "fake" or psuedo ethernet driver that simply sits as a shim
> between one or more real drivers. This fake device could allow us to
> "Stack" qdiscs in a way to allow one to shape traffic in multiple
> "policies" - ie, prioritize traffic AND allocate / rate shape end users.
> I have actually thought of utilizing the kernel bonding driver for this -
> attaching only a single slave to it - but haven't had time as yet. Not
> sure that this would do anything for ingress shaping though.
>
I have been working on this with using what I call a ppp-pipe. The result
is
Internet (eth0) <-> ppp0 ----- ppp1 <-> LAN (eth1) 10.0.0.0/8
where ppp0----ppp1 is on the local machine (and simulates two NICs with a
crossover cable between them in the same machine). What you throw in at
ppp0
appears at ppp1 and vice versa. This works fine, it also means you can
shape
on the ppp0/ppp1 interfaces and leave all the NAT stuff on the real
interfaces.
The command to create this ppp-pipe is (as root), so far I am not completely
sure if you need to add to the first pppd command "<real ip>:<real ip>" for
its parameters (you might also need 'xonxoff' too in both):
# mkfifo /tmp/ppp-pipe
# pppd noauth nodefaultroute notty < /tmp/ppp-pipe | pppd noauth \
notty > /tmp/ppp-pipe
However there is a major problem......connection tracking. In the above
setup you do
iptables -t nat -I POSTROUTING -s 10.0.0.0/8 \
-d ! 10.0.0.0/8 -o eth0 -j MASQUERADE
the '-o eth0' is very important, you also create some advance routing bits
to
make all traffic crossing the router to pass through the ppp-pipe; easy
enough, but depends on your needs. Conntrack unfortunately notices that you
did not want to NAT the packet straight away when it arrives on eth1 (if you
do then you will be unable to shape fairly per IP, for example with ESFQ),
but then later on when the packet resurfaces at ppp0 the 'nat' table is
skipped. The only way about this is to use the patch-o-matic RAW patch and
instruct it to skip connection tracking for packets on eth1 destined for the
Internet.
As I am now pure 2.6.x goodness I am in the middle of porting the patch
myself (the patch-o-matic-ng does not work for me, could be me being lame
though).
Sure this is replacing one patch dependency with another, however IMQ really
seems that it has been left out to rot; whilst the RAW patch probably is
going to stay better maintained, hell its in the patch-o-matic for starters.
Besides there are lots of advantages with the ppp-pipe, as now all you folks
who want to shape over with IP-Aliasing can just use cunning ppp-pipes
instead; whilst still keeping things very simple. So far the above should
work in non-NAT (or rather connection tracking) setups but where you want
the
equilivent of IP-Aliased style shaping.
Anyway thoughts would be apprieated, however when I was on #lartc it was its
normal dead self so I was left dead in the water myself :(
have fun
Alex
--
___________________________
< Fortune favors the lucky. >
---------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply
* Re: REISER4 corruptions errors
From: Alex Zarochentsev @ 2004-01-26 15:51 UTC (permalink / raw)
To: Carl-Daniel Hailfinger; +Cc: Paolo Correnti, REISER LIST
In-Reply-To: <401541FA.5060309@gmx.net>
On Mon, Jan 26, 2004 at 05:36:10PM +0100, Carl-Daniel Hailfinger wrote:
> Alex Zarochentsev wrote:
>
> > this patch should help (! not tested):
> >
> > ===== tree.c 1.562 vs edited =====
> > --- 1.562/tree.c Wed Jan 14 11:46:20 2004
> > +++ edited/tree.c Mon Jan 26 18:24:39 2004
> > @@ -1468,7 +1468,7 @@
> > if ((result != 0) && (result != -E_NO_NEIGHBOR))
> > break;
> > /* Check can we delete the node as a whole. */
> > - if (iterations && znode_get_level(node) == LEAF_LEVEL &&
> > + if (0 && iterations && znode_get_level(node) == LEAF_LEVEL &&
> > UNDER_RW(dk, current_tree, read,
> > keyle(from_key, znode_get_ld_key(node)))) {
> > result = delete_node(next_node_lock.node,
>
> Was it your intention to disable the above code path?
no, it will be fixed in proper way. my fix is a temporary solution.
--
Alex.
^ permalink raw reply
* Re: PATCH: (as177) Add class_device_unregister_wait() and platform_device_unregister_wait() to the driver model core
From: Alan Stern @ 2004-01-26 15:51 UTC (permalink / raw)
To: Rusty Russell; +Cc: Greg KH, torvalds, linux-kernel, mochel
In-Reply-To: <20040126165035.2fda1b3e.rusty@rustcorp.com.au>
On Mon, 26 Jan 2004, Rusty Russell wrote:
> If you want to safely remove parts of the kernel, you have to maintain
> reference counts. At least with any sane scheme I've seen.
>
> I know, I should go read the code...
> Rusty.
The problem I raised originally is that in many cases the reference count
can't be maintained properly without preventing the module from ever
exiting at all. The difficulty is that the reference count won't go
down to 0 until the module code deregisters itself from some list. But
the deregistration only happens within the module's exit routine!
A two-step exit process, like that used for kobjects, would avoid this
difficulty. During the first step the module would deregister itself.
The second step, unloading from memory, would occur when the reference
count was 0.
Contrary what Linus said, in many modules it's not necessary to update the
module's reference count with every single transaction (packet or
whatever) that goes through. Usually a single registration event, or just
a small handful, is critical for unloading.
A good case in point is the one that led to the start of this thread. A
USB host controller driver registers a USB bus that it will manage, and
from then on it handles lots of USB packets. It's not necessary to update
the driver module's reference count with every packet; all that matters is
that the module has to wait for the bus to be released before it can be
unloaded from memory. (That's because existing mechanisms cause each
packet to hold a reference to a USB device and the device holds a
reference to the bus.) For lack of any other way to avoid exiting early
we simply have to wait for the bus's release callback to finish -- not
waiting will cause a kernel panic if the module unloads before the release
method runs.
Furthermore, in other cases where it _is_ necessary to update a reference
count with every packet, it's not necessary that doing so involve a lot of
additional overhead such as acquiring a lock of some sort. If some
driver, like a network interface driver, is managing lots of packets then
it must _already_ be using a lock to keep track of things like the total
number of outstanding packets. Any extra work could be done under the
protection of this pre-existing lock and would involve minimal overhead.
One aspect of what Linus wrote is absolutely right, however: Getting this
to work right, for all the loadable kernel modules, would be quite
difficult. Here's one way to attack that, an incremental approach.
Create a new module entry point, the module_unreg routine. For all
existing modules this entry point would be undefined and hence not used.
The module_unreg routine is called to start the deregistration process,
invoked say by some special flag to rmmod. The module_exit routine would
then be called when an unregistered module's reference count dropped to 0.
Existing modules would experience exactly the same sequence of events as
they do now, and newly-written modules could take advantage of the extra
mechanism.
Admittedly, this is just a theoretical exercise. Linus said that module
unloading should basically be unsupported. I have no doubt that making it
even more complicated, like this, is not something he would approve of.
Alan Stern
^ permalink raw reply
* Re: ax25 support in aprsd
From: Adi Linden @ 2004-01-26 15:51 UTC (permalink / raw)
To: John Williams; +Cc: linux-hams
In-Reply-To: <401561ED.23331.F6ED65@localhost>
Thank you for the explanation. My support for all this aprs stuff are the
various mailing lists. I am in a somewhat remote place, the only aprs
station in the area is the tracker in my van and the occassional visitor.
I guess I don't really need a digi a simple aprsd igate should do. But it
is something interesting to do and eventually I'd like to support
satellite traffic, too.
> gate2rf VK5* PC* W3ADO* RS0ISS* ARISS* WU2Z
> #gate2rf VK5*
I have a question about gating to rf, now that it has been mentioned. Is
it possible to gate packets that were gated to TCP/IP by another specific
igate? There is another igate about 100km away and out of RF reach.
Thanks,
Adi
^ permalink raw reply
* Re: IMQ Replacement
From: Andy Furniss @ 2004-01-26 15:50 UTC (permalink / raw)
Cc: Netfilter Mailing List
In-Reply-To: <20040126144206.GA11104@zion.homelinux.com>
Sven Schuster wrote:
> Hi Andre,
>
> maybe interessting for you: Marcel Sebek recently started a thread
> on netdev about this topic. He has ported the IMQ device to 2.6
> and asked if this might be accepted. Davem contacted Patrick
> McHardy, the original author, who said that the IMQ device was
> buggy.
> This thread still continues, take a look at netdev ml archives for
> more information.
There is also discussion on the LARTC list at the moment - someone
called roy has rewritten IMQ but still sees crashes. He thinks they are
related to locally generated traffic, so IMQ for ingress should be OK.
Personally I have used IMQ for locally generated traffic (> a gig/day up
with bittorrent running on a P200 gateway) without problems, but I only
have 256kbit/s up and shutdown everything at night.
Andy.
>
> HTH
>
> Sven
>
> On Mon, Jan 26, 2004 at 10:16:55AM -0200, Andre Correa told us:
>
>>Hi guys, Andy F. pointed out that Alexander Clouter and other guys
>>ported IMQ to 2.6. The URL to their port is:
>>
>>http://www.digriz.org.uk/jdg-qos-script/#qos-2.6
>>
>>I had no time or resources to test it so far...
>>
>>I've got no answer from the last IMQ maintainer so I'll start a list for
>>us to discuss what we'll gonna do about it. I'll let you know later today.
>>
>>I'm sorry if this thread is disturbing somebody in this list. I'll just
>>post 1 or 2 e-mails about it and we'll be out...
>>
>>Meanwhile, anybody interrested in joining us to work with IMQ please
>>contact me privately.
>>
>>tks...
>>
>>Andre
>
>
^ permalink raw reply
* Re: howto configuring kernel and modules.conf for automatic loading of ide-scsi
From: Ken Moffat @ 2004-01-26 15:50 UTC (permalink / raw)
To: Agri; +Cc: linux-newbie
In-Reply-To: <20040126124651.5c1aa170.agri@desnol.ru>
On Mon, 26 Jan 2004, Agri wrote:
> Oh.... i did everything as you say many times before...
> i get success only this time.
> i have done a little investigation...
> there is no need of
> pre-install sg modprobe ide-scsi # load ide-scsi before sg
> pre-install sr_mod modprobe ide-scsi
> moreover these lines breaks loading after "rmmod -a"
Ok,
if you don't need them, don't use them! At one time they appeared to
be necessary for me (although I was also doing some other stuff for my
ide zip drive, which I cut out of the example). I've never
intentionally used rmmod for these things, so it doesn't surprise me
that I can break it :) Maybe you need to tell rmmod to remove each of
these modules, not just the 'top level'. Module loading has always been
one of the harder things to find accurate information for.
Ken
--
This is a job for Riviera Kid!
-
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: Application Problems with Reiser4/19.01.2004-fixed (truncated)
From: Willi W. @ 2004-01-26 15:46 UTC (permalink / raw)
To: reiserfs-list
In-Reply-To: <16401.3844.21706.388236@laputa.namesys.com>
Hi!
>Hmm... can you run overnet under strace (up to the failure) and send the
>output to me?
--
all files in the ./temp directory should be reloaded at startup.
access to the directory in the strace output:
--
--
[pid 21379] <... write resumed> ) = 1
[pid 21381] stat64("/mnt/reiser4/overtest/temp", <unfinished ...>
[pid 21379] write(0, "n", 1n <unfinished ...>
[pid 21381] <... stat64 resumed> {st_mode=S_IFDIR|S_ISVTX|0755,
st_size=3, ...}) = 0
[pid 21379] <... write resumed> ) = 1
[pid 21381] open("/mnt/reiser4/overtest/share.dat", O_RDONLY
<unfinished ...>
[pid 21379] write(0, "e", 1e <unfinished ...>
[pid 21381] <... open resumed> ) = 6
[pid 21379] <... write resumed> ) = 1
[pid 21381] lseek(6, 0, SEEK_CUR <unfinished ...>
[pid 21379] write(0, "t", 1t <unfinished ...>
[pid 21381] <... lseek resumed> ) = 0
--
i cannot tell if this is correct (stat64...=0)
the whole strace is attached. (sent to nikita)
after the test, the filesystem was _corrupt again_ (wasnt before) - fscp
output attached (also sent to nikita)
...
Error: Node (23), item (4): StatData of the file
[100de:636f6e74616374:100f1] has the wrong bytes (96966), Should be
(11504).
Plugin (stat40).
Error: Node (23), item (5): StatData of the file
[100de:667269656e642e:100f3] has the wrong bytes (55), Should be
(5). Plugin
(stat40).
...
--
p.s. i have harddrive writecache turned on - is this good/bad/should'nt
matter ? (again - no problems under reiser3)
hdparm /dev/hdb
/dev/hdb:
multcount = 16 (on)
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
readahead = 256 (on)
geometry = 39770/16/63, sectors = 40088160, start = 0
AdvancedPM=no WriteCache=enabled
regards
Willi
^ permalink raw reply
* Re: problems connecting to kernel.bkbits.net
From: Larry McVoy @ 2004-01-26 15:41 UTC (permalink / raw)
To: linux-kernel
Eric forwarded me this mail (thanks).
The BK->CVS gateway is still going strong but the CVS server part of it has
been shut down because of security problems. Nobody wants to run it because
of the security problems that CVS has. If someone wants to do that they
can mirror it from kernel.org, it's there under /pub/scm/linux/kernel/bkcvs
and if you grab that you can start up a CVS server.
----- Forwarded message from Stas Sergeev <stsp@aknet.ru> -----
From: Stas Sergeev <stsp@aknet.ru>
To: linux-kernel@vger.kernel.org
Subject: problems connecting to kernel.bkbits.net
Date: Sun, 25 Jan 2004 20:11:35 +0300
Hello.
I used a BK->CVS gateway on kernel.bkbits.net
for some time, but it is already several
month that I can't connect to it any more.
Is it still alive?
Here is what I have:
$ cvs update
cvs [update aborted]: connect to kernel.bkbits.net(192.132.92.14):2401
failed: No route to host
$ traceroute kernel.bkbits.net
1 gate (192.168.3.1) 5.823 ms 16.544 ms 8.973 ms
2 RINNet-MSU.iitp.ru (194.220.14.45) 12.531 ms 143.000 ms 69.300 ms
3 RINNet-IITP.iitp.ru (194.220.14.129) 134.844 ms 212.712 ms
190.928 ms
[.....]
20 svl-edge-09.inet.qwest.net (205.171.14.98) 312.245 ms * 204.768 ms
21 63.150.59.90 (63.150.59.90) 268.390 ms 217.756 ms 218.520 ms
22 216.240.36.206 (216.240.36.206) 218.669 ms 248.692 ms 218.659 ms
23 kernel.bkbits.net (192.132.92.14) 214.393 ms !<10> 243.426 ms
!<10> *
$ ping kernel.bkbits.net
PING kernel.bkbits.net (192.132.92.14) from 192.168.3.28 : 56(84)
bytes of data.64 bytes from kernel.bkbits.net (192.132.92.14):
icmp_seq=0 ttl=44 time=239.295 msec
64 bytes from kernel.bkbits.net (192.132.92.14): icmp_seq=1 ttl=44
time=230.619 msec
--- kernel.bkbits.net ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/mdev = 230.619/234.957/239.295/4.338 ms
Now I am lost. ping is fine, but traceroute
shows code 10, which is "Host prohibited".
Any ideas what can that be?
I have googled a lot, but I have found
nothing that looks even nearly similar to the
problem I am having.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
----- End forwarded message -----
^ 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.