Messages in this thread | | | Subject | Re: [PATCH] de4x5.c [was Re: pre-2.1.116-1 breaks Cyrix 6x86 support] | From | Zlatko Calusic <> | Date | 11 Aug 1998 20:46:50 +0200 |
| |
Gabriel Paubert <paubert@iram.es> writes:
> On 11 Aug 1998, Zlatko Calusic wrote: > > > Linus, could you please apply appended patch to de4x5.c, unless David > > has even newer version (even though this one works perfectly). > > > > Patch allows the kernel to be compiled with egcs/pgcc/gcc 2.8 (without > > it kernel would Oops in the early booting stage) and helps to get rid > > of the annoying messages also during boot stage (see below). David > > wrote the patch, I'm just trying to get it in before the code freezes. :) > > As author of the *kludge* that allows the driver to be succesfully > compiled with egcs/pgcc/gcc-2.8.x, I have to shout as loudly as I can that > it is intrinsically UNSAFE. It is a workaround that happens to work by > sheer luck, I came to it after quite a large number of experiments > compiling the driver and reading the generated assembly.
Well, a big THANK YOU to your kludge, since I *finally* can compile kernel with egcs and be really happy.
Of course, you're a nice guy to tell us about possible problems. But my Linux is running great, really.
I saw lots of your messages in the archives, about problems with egcs and so, but never really found magic "string.h/egcs" patch. Now, it looks, I have it, hiding somewhere in that small patch. :)
Thanks, once again.
> > Any newer version of these compilers might break the driver again (or for > that matter many things using string functions in asm-i386/string.h). > Something has to be done about string.h before 2.2 anyway. > > Ok, you've been warned :-)
:)
> > > > without the patch: > > > > eth1: region already allocated at 0xec00. > > eth1: region already allocated at 0xec00. > > eth2: region already allocated at 0xec00. > > eth3: region already allocated at 0xec00. > > ... > > eth7: region already allocated at 0xec00. > > > > Zlatko, please take the code freeze for what it is ;-) Don't forget what > Linus said when 2.1.115 came out: > `Bug-fixes are still (and will always be) accepted'
Should I keep this sentence for my tag generator? :)
> > The fix to the multiple eth found is _obviously_ a bug fix.
Yeah, sure. Why don't we wait 2.1.116 and see. :)
But, of course, David has the final word. He is maintainer, I'm pushing my luck, only. :)
Sometimes, problem is that you have too many patches to apply to your kernel. I'm currently patching for PnP, de4x5, my small MM change, one to Makefiles + random fixes to things that break on some particular kernel (living on the bleeding edge).
So one looses lots of time porting that patches to every new kernel release. I hope it's obvious that more you put in the official kernel, less work remains to yourself. And more time to (try to) develop a nice new things, to benchmark and read linux-kernel.
<MODE="little weasel"> When you have everything in the kernel, you just let Linus worry about things. He's good at it. Good? He's the best! :) </MODE>
Keep up the good work! -- Posted by Zlatko Calusic E-mail: <Zlatko.Calusic@CARNet.hr> --------------------------------------------------------------------- I've been typing so long my fingers have letters on them.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
| |