tool to keep multiple architectures/kernel configs straight?

Supporting a number of kernels/platforms there are: 1) common options (which should be all the same across all platforms) 2) platform/processor specific options 3) some options are common across kernel versions but not across all versions Is there a good way to maintain this

power off disk drives while running

In embedded system design, it may be useful to poweroff the disks (as opposed to merely spinning them down). We want to leave the system running while the disk is powered down, and let the disk powerup when it needs to be spun up. While the "power off mechanism" would be platform dependent, is

working sata_vsc driver with 2.6.20?

I'm having a hell of a time with the sata_vsc driver with 2.6.20... 2.6.21 works fine --but the driver is radically different -- is there a method to build the 2.6.21 driver against 2.6.20? There are a number of patches on the 2.6.20 sata driver (it works on a PC platform, but fails with our embe

Re: ownership/permissions of cpio initrd

Jeffrey Hundstad <[EMAIL PROTECTED]> writes on Tue, 05 Dec 20 06 14:17:22 CST > You can also use fakeroot(1). > > Start fakeroot. > Change all of your permissions as you see fit. > make your cpio > exit fakeroot. > > > ThanksI got it running on

ownership/permissions of cpio initrd

I'm working on an embedded system with the 2.6 kernel -- cpio initrd was a new feature I'm looking at (and very welcome). The major advantage I see is you don't have MAKE a filesystem on the build host (doing cross development). So you don't have to be root. But its "useful" to change permission

PCI bridge devices questions

4) would it make more sense to have seperate arrays? One of for the device resources, one for the bridge resources? Thanks... Marty Leisner [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTE

mounting a fs in two places at once?

2,maxproto=3) pb:(pid704) on /net type nfs (intr,rw,port=1023,timeo=8,retrans=110,indirect,ma p=/etc/amd.net,dev=0007) /dev/hda10 on /mnt type ext2 (rw) /dev/hda10 on /home type ext2 (rw) Is this a feature or a bug? This is with 2.4.2... Marty Leisner [EMAIL PROTECTED] - To unsubscribe

what's the purpose of SYMBOL_NAME()

I'm read Bovet's "Understand the Linux Kernel" and looked at the assembly routine setup_idt... I noticed the assembly has SYMBOL_NAME (its all over the place). This is define in include/linux/linkage.h to just: #define SYMBOL_NAME(X) X (this wasn't in Bovet's book). What's the purpose? m

Re: Wow! Is memory ever cheap!

I'm confused by the "lets not use ECC and use bk" talk. My understanding is suns big machines stopped using ecc and they started to have "random" problems running big-iron applications that took them a while to figure out (and a lot of bad press) and can only be rectified in the big cycle (this

Re: kernel threads and close method in a device driver

Marty - --- Forwarded Message To: Andi Kleen <[EMAIL PROTECTED]> Subject: Re: kernel threads and close method in a device driver In-Reply-To: Your message of "Tue, 17 Apr 2001 23:43:39 +0200." <[EMAIL PROTECTED]> Date: Wed, 18 Apr 2001 10:49:04 -0400 From: "Marty

kernel threads and close method in a device driver

I'm involved with modifying a device driver for new hardware. The architecture is currently: open device do IOCTL (spinning a kernel thread and doing initialization) There is currently an IOCTL which short-circuits to the close method. Turns out it seems necessary to do this IO

bizarre problems with Athlon system after upgrdaing motherboard

At work, we're using a AMD Athlon system for evaluation. Our last motherboard didn't work with 512Mbyte simms, so we got a new motherboard (an Asus flavor -- the old motherboard only saw 256 Mbyte). I had Redhat 6.2 installed (2.2.14). It worked fine. When we upgraded the motherboard, we got