Re: Microsoft and Xenix.
> "rob" == Rob Landley <[EMAIL PROTECTED]> writes: rob> On Saturday 23 June 2001 22:47, Eric W. Biederman wrote: >> Rob Landley <[EMAIL PROTECTED]> writes: >> > Ummm... GEM was the Geos stuff? (Yeah I remember it, I haven't >> > researched it yet though...) >> >> GEM was a gui from Digital Research I believe. >> Geoworks/Geos was a seperate entity. rob> Ah, the DR-DOS answer to dosshell/windows. Cool. (I used Dr. Dos byt never rob> tried its gui.) Nope. GEM is older that dosshell, if I remember correctly, dosshell appeared with dos 4.x, and GEM was there with DOS 3.x (was x = 22?). I also had DOS+ from Digital Research in my Amstrad PC1512. Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Cosmetic JFFS patch.
> "ian" == Ian Stirling <[EMAIL PROTECTED]> writes: Hi ian> It would be nice to show driver version for every single non-stock ian> driver we load though. ian> Perhaps a list of versions in the stock kernel build, stored somewhere, ian> that shouldn't be patched by anyone, but only change with official releases. ian> At compile time, if the driver version string is different from the ian> 'blessed' version, it prints it's version, and possibly more. Don't work, because the kernels in distributions are heavily patched, and for the distribution the driver that counts is the one that is in in the distribution, not the one in standard kernel. I think that this is overengenering and not too useful :( Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] fix for initrd panic in 2.4.5
> "james" == James Bottomley <[EMAIL PROTECTED]> writes:
james> Not many people have seen this, but the i_bdev field in fake_inode in
james> ioctl_by_bdev() is uninitialised. Since this field is dereferenced by
james> BLKFLSBUF in rd_ioctl, it can lead to a panic (depending on what happens to be
james> on the stack). The attached fixes the problem and clears all the fields in
james> fake_inode to make any other problems like this show up.
see the fix in ac kernels, you have a bdev there to put in the
fake_inode.
Later, Juan.
james> Index: fs/block_dev.c
james> ===
james> RCS file: /home/jejb/CVSROOT/linux/2.4/fs/block_dev.c,v
james> retrieving revision 1.1.1.10
james> diff -u -r1.1.1.10 block_dev.c
james> --- fs/block_dev.c 2001/05/26 15:33:37 1.1.1.10
james> +++ fs/block_dev.c 2001/06/02 13:14:35
james> @@ -596,13 +596,14 @@
james> int ioctl_by_bdev(struct block_device *bdev, unsigned cmd, unsigned long arg)
james> {
james> kdev_t rdev = to_kdev_t(bdev->bd_dev);
james> -struct inode inode_fake;
james> +struct inode inode_fake = { 0 };
james> int res;
james> mm_segment_t old_fs = get_fs();
james> if (!bdev->bd_op->ioctl)
james> return -EINVAL;
james> inode_fake.i_rdev=rdev;
james> +inode_fake.i_bdev = bdev;
james> init_waitqueue_head(&inode_fake.i_wait);
james> set_fs(KERNEL_DS);
james> res = bdev->bd_op->ioctl(&inode_fake, NULL, cmd, arg);
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] warning fixes for 2.4.5pre5
Hi > --- linux/arch/i386/math-emu/fpu_trig.c Fri Apr 6 12:42:47 2001 > +++ rb/arch/i386/math-emu/fpu_trig.c Tue May 22 16:44:57 2001 > @@ -1543,6 +1543,7 @@ > EXCEPTION(EX_INTERNAL | 0x116); > return; > #endif /* PARANOID */ >+return; > } > } > else if ( (st0_tag == TAG_Valid) || (st0_tag == TW_Denormal) ) Will not be better to move the return out of the #endif PARANOID? Otherwise you get 2 returns when you have defined paranoid ... > --- linux/drivers/scsi/sym53c8xx.cFri Apr 27 15:59:19 2001 > +++ rb/drivers/scsi/sym53c8xx.c Tue May 22 16:45:03 2001 > @@ -11564,6 +11564,7 @@ > OUTL_DSP (NCB_SCRIPT_PHYS (np, clrack)); > return; > out_stuck: >+ return; > } same Later,Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Dying disk and filesystem choice.
> "erik" == Erik Mouw <[EMAIL PROTECTED]> writes: erik> On Thu, May 24, 2001 at 09:53:45AM -0700, Hans Reiser wrote: >> No, reiserfs does have badblock support >> >> You just have to get it as a separate patch from us because it was >> written after code freeze. erik> IMHO we are not that deep into code freeze anymore. Freevxfs got added erik> in linux-2.4.5-pre*, so I think that a patch that adds a useful feature erik> like badblock support would be OK. A new filesystem don't touch anything if you don't use it. Some reasoning for inclusion of new drivers. Big changes in a working driver could make it not to work (very bad in the stable series). Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH] hga depmod fix
Hi if you compile hga as a module, you get unresolved symbols, you need the following patch for it. The patch is trivial. Apply, please. Later, Juan. --- linux/drivers/video/hgafb.c.~1~ Mon May 21 08:56:08 2001 +++ linux/drivers/video/hgafb.c Mon May 21 09:04:00 2001 @@ -712,7 +712,7 @@ hga_gfx_mode(); hga_clear_screen(); -#ifdef MODULE +#ifndef MODULE if (!nologo) hga_show_logo(); #endif /* MODULE */ -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.3-p8 pci_fixup_vt8363 + ASUS A7V "Optimal" = IDE disk corruption
Hi
sorry for the delay, it is working for your motherboard the
lastest kernels of Mandrake? I think that all the problems
have been solved?
Sorry for the delay, as I was finishing more things.
Later, Juan.
>>>>> "wayne" == Wayne Whitney <[EMAIL PROTECTED]> writes:
wayne> On 29 Mar 2001, Juan Quintela wrote:
>> Hi I have the same motherboard and BIOS version. I was having
>> filesystem corruption. There is a bugfix (from Arjan van der Ven) in
>> the ac tree (around ac20 I think), could you test the last ac patch
>> and test if the filesystem corruption persist??
wayne> I took a look at 2.4.2-ac28; rather than test the kernel itself, I used
wayne> setpci to duplicate what the fixup function does. The upshot is that
wayne> 2.4.2-ac28 does not cause any corruption with the ASUS A7V 1007 "Optimal".
wayne> Its pci_fixup_vt8363 function has a subset of the tests from 2.4.3-pre8,
wayne> namely it omits:
wayne> pci_read_config_byte(d, 0x54, &tmp);
wayne> if(tmp & (1)) {
wayne> printk("PCI: Fast Write to Read turnaround disabled\n");
wayne> pci_write_config_byte(d, 0x54, tmp & ~(1));
wayne> }
wayne> pci_read_config_byte(d, 0x70, &tmp);
wayne> if(tmp & (1<<2)) {
wayne> printk("PCI: Disabled Master Read Caching\n");
wayne> pci_write_config_byte(d, 0x70, tmp & ~(1<<2));
wayne> }
wayne> This second test was part of the 2.4.3-pre8 pci_fixup_vt8363 subset from
wayne> my previous email which causes corruption on the ASUS A7V 1007 for both
wayne> Optimal and Normal settings. I verified that if I add it back in, I do
wayne> get corruption with ASUS A7V 1007 "Optimal". By omitting it, I guess
wayne> 2.4.2-ac28 avoids the corruption of 2.4.3-pre8.
wayne> Perhaps 2.4.3-pre9 should adopt the pci_fixup_vt8363 from 2.4.2-ac28?
wayne> Below is a patch.
wayne> Cheers,
wayne> Wayne
wayne> --- linux-2.4.3-pre8/arch/i386/kernel/pci-pc.c Wed Mar 28 22:56:04 2001
wayne> +++ linux-2.4.2-ac28/arch/i386/kernel/pci-pc.c Wed Mar 28 22:51:00 2001
wayne> @@ -968,23 +971,13 @@
wayne> printk("PCI: Bus master Pipeline request disabled\n");
wayne> pci_write_config_byte(d, 0x54, tmp & ~(1<<2));
wayne> }
wayne> -pci_read_config_byte(d, 0x54, &tmp);
wayne> -if(tmp & (1)) {
wayne> -printk("PCI: Fast Write to Read turnaround disabled\n");
wayne> -pci_write_config_byte(d, 0x54, tmp & ~(1));
wayne> -}
wayne> pci_read_config_byte(d, 0x70, &tmp);
wayne> if(tmp & (1<<3)) {
wayne> printk("PCI: Disabled enhanced CPU to PCI writes\n");
wayne> pci_write_config_byte(d, 0x70, tmp & ~(1<<3));
wayne> }
wayne> -pci_read_config_byte(d, 0x70, &tmp);
wayne> -if(tmp & (1<<2)) {
wayne> -printk("PCI: Disabled Master Read Caching\n");
wayne> -pci_write_config_byte(d, 0x70, tmp & ~(1<<2));
wayne> -}
wayne> pci_read_config_byte(d, 0x71, &tmp);
wayne> -if ((tmp & (1<<3))==0) {
wayne> +if((tmp & (1<<3)) == 0) {
wayne> printk("PCI: Bursting cornercase bug worked around\n");
wayne> pci_write_config_byte(d, 0x71, tmp | (1<<3));
wayne> }
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: kdb wishlist
> "slurn" == slurn <[EMAIL PROTECTED]> writes: >> >> Keith Owens wrote: >> > >> > This is part of my kdb wishlist, does anybody fancy writing the code to >> > add any of these features? It would be a nice project for anybody >> > wanting to start on the kernel. Replies to [EMAIL PROTECTED] please. >> > Current patches at http://oss.sgi.com/projects/kdb/download/ >> > >> > * Change kdb invocation key from ^A to ^X^X^X within 3 seconds. ^A is >> > used by emacs, bash, minicom etc. >> > >> ^X^X swaps point and mark in emacs. One (well, I) often will do >> ^X^X^X^X to examine where mark is and then return to point. slurn> How about using the break condition instead. This is only for the slurn> serial port, and most terminal emulators (e.g. kermit, minicom) provide slurn> a means to generate a break condition on the serial port. kdb uses BREAK in the serial port (that minicom uses C-a for sending a break is an anecdote :) But the problem at hang is the console. I vote for the ^X^X^X as I a think that it is not a difficult shortcut. (and yes, I also use emacs and ^X^X all the time, but I think that this combination is not specially bad, and I suppose that the pet aplication of other people will have problems with something like: ^A^A^A that I never use). Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Requirement of make oldconfig [was: Re: [kbuild-devel] Re: CML2 1.3.1, aka ...]
> "horst" == Horst von Brand <[EMAIL PROTECTED]> writes: Hi horst> Hell, I had to rebuild my .config files from scratch a few times already horst> because of wild changes in the hardware on which the resulting kernels horst> would have to run, its not _that_ big a deal to have to perhaps have to do horst> it once each time a new stable kernel series starts or so. Not a option. You can have to had _several_ configurations around (here at MandrakeSoft we have normal/smp/enterprise) and we have basically everything that can be compiled as modules compiled as modules. Add to that that we build the alpha (normal&smp) from the same package. We want to add more architectures to the rpm. Are you really serious that _answering_ all the options for several kernels is an option? I don't think so. And the actual olconfig target works well for me (tm). I don't see the point to rewrote the configuration language and made it _less_ powerfull for no good reason. Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
