View previous topic :: View next topic |
Author |
Message |
nevynxxx Veteran
Joined: 12 Nov 2003 Posts: 1123 Location: Manchester - UK
|
Posted: Wed Feb 25, 2004 8:50 am Post subject: |
|
|
Steel since porsting the notes.txt for each release is now obviously too long, and we are getting people askin whats in love. Please find below how I see whats in a specific release. It may be useful to post the output of this. Its quite a lot shorter.
Code: | grep Description 2.6.3-love4-notes.txt | sed 's/Description:\ //' |
Note this is written for bash in cygwin (as I usually grab new lov's from work), so no doubt something has to change.[/code] _________________ My Public Key
Wanted: Instructor in the art of Bowyery |
|
Back to top |
|
|
eldiablo Tux's lil' helper
Joined: 20 Sep 2003 Posts: 136 Location: Halsa(Where keiko lived his last days), Norway
|
Posted: Wed Feb 25, 2004 12:35 pm Post subject: |
|
|
How is it with this kexec thing? is someone looking at it at the time beeing?
It would be nice to have it back, stable. _________________ Always running the most experimental |
|
Back to top |
|
|
Master_Of_Disaster l33t
Joined: 28 Feb 2003 Posts: 610 Location: 15.05072° East, 48.13747° North (aka Mauer), Austria
|
Posted: Wed Feb 25, 2004 1:23 pm Post subject: |
|
|
Nobody reacted to my previous post regarding this problem, so I'll be nagging once again:
Code: | CC arch/x86_64/kernel/syscall.o
arch/x86_64/kernel/syscall.c:28: error: `__ioprio_get' undeclared here (not in a function)
arch/x86_64/kernel/syscall.c:30: error: nonconstant array index in initializer
arch/x86_64/kernel/syscall.c:30: error: (near initialization for `sys_call_table')
In file included from arch/x86_64/kernel/syscall.c:31:
include/asm-x86_64/unistd.h:16: error: array index in non-array initializer
include/asm-x86_64/unistd.h:16: error: (near initialization for `sys_call_table')
include/asm-x86_64/unistd.h:16: warning: excess elements in scalar initializer
include/asm-x86_64/unistd.h:16: warning: (near initialization for `sys_call_table') |
Tried with both gcc 3.3/3.4 on an AMD 64. _________________ post tenebras lux, post fenestras tux
Registered Linux User Nr. 312509
Adopt an unanswered post today! |
|
Back to top |
|
|
c0bblers Guru
Joined: 28 Mar 2003 Posts: 403
|
Posted: Wed Feb 25, 2004 2:23 pm Post subject: |
|
|
Hi,
Just thought I'd point out that there's an updated pktcdvd patch at http://w1.894.telia.com/~u89404340/patches/packet/2.6/ for the 2.6.3 kernel. I doubt it does much more than rejig the patch for the newer kernel though from what the changelog says.
Cheers,
James |
|
Back to top |
|
|
Spawn of Lovechild Apprentice
Joined: 03 Feb 2004 Posts: 253 Location: Århus, Denmark
|
Posted: Wed Feb 25, 2004 2:32 pm Post subject: |
|
|
eldiablo wrote: | How is it with this kexec thing? is someone looking at it at the time beeing?
It would be nice to have it back, stable. |
kexec is nowhere near ready, right now it's a nice fix for older machines that doesn't support the halting process used by Linux, but getting to the point where we can replace a running kernel is a long way away. _________________ Proud to be a 22 year old Infidel, GNOME lover and member of LIK. |
|
Back to top |
|
|
steel300 Veteran
Joined: 10 Jul 2003 Posts: 1155
|
Posted: Wed Feb 25, 2004 2:48 pm Post subject: |
|
|
GentooBox wrote: | GentooBox wrote: | @steel300
why did you remove nforce2-apic.patch and nforce2-disconnect-quirk.patch from your kernel ?
BTW: Do you have the patches somewhere ? if you do, please upload them or send them to my email. i need them, or else my new kernel breaks. |
Any chance in getting an answer ? |
Sorry for taking so long. I was under the impression that the nforce patches were included with mm. IIRC, they were at one point, then removed, then added again, now it looks like they're removed. I'll upload them to the linuxmall site and you can patch them. I will include them in future releases. _________________ Rationality is the recognition of the fact that nothing can alter the truth and nothing can take precedence over that act of perceiving it. |
|
Back to top |
|
|
steel300 Veteran
Joined: 10 Jul 2003 Posts: 1155
|
Posted: Wed Feb 25, 2004 2:50 pm Post subject: |
|
|
Master_Of_Disaster wrote: | Nobody reacted to my previous post regarding this problem, so I'll be nagging once again:
Code: | CC arch/x86_64/kernel/syscall.o
arch/x86_64/kernel/syscall.c:28: error: `__ioprio_get' undeclared here (not in a function)
arch/x86_64/kernel/syscall.c:30: error: nonconstant array index in initializer
arch/x86_64/kernel/syscall.c:30: error: (near initialization for `sys_call_table')
In file included from arch/x86_64/kernel/syscall.c:31:
include/asm-x86_64/unistd.h:16: error: array index in non-array initializer
include/asm-x86_64/unistd.h:16: error: (near initialization for `sys_call_table')
include/asm-x86_64/unistd.h:16: warning: excess elements in scalar initializer
include/asm-x86_64/unistd.h:16: warning: (near initialization for `sys_call_table') |
Tried with both gcc 3.3/3.4 on an AMD 64. |
Could you make your config file available (preferably on an off site link). I haven't run into any errors when compiling for an AMD64, so I'll try it with your config and see what I can dig up. _________________ Rationality is the recognition of the fact that nothing can alter the truth and nothing can take precedence over that act of perceiving it. |
|
Back to top |
|
|
ledskof Apprentice
Joined: 22 Oct 2002 Posts: 209
|
|
Back to top |
|
|
Master_Of_Disaster l33t
Joined: 28 Feb 2003 Posts: 610 Location: 15.05072° East, 48.13747° North (aka Mauer), Austria
|
Posted: Wed Feb 25, 2004 3:15 pm Post subject: |
|
|
steel300 wrote: | Could you make your config file available (preferably on an off site link). I haven't run into any errors when compiling for an AMD64, so I'll try it with your config and see what I can dig up. |
Thanks very much steel, you can find my config here.
I forgot to mention that -mm3 compiles fine with this config. _________________ post tenebras lux, post fenestras tux
Registered Linux User Nr. 312509
Adopt an unanswered post today! |
|
Back to top |
|
|
gringo Advocate
Joined: 27 Apr 2003 Posts: 3793
|
Posted: Wed Feb 25, 2004 4:53 pm Post subject: |
|
|
Well, kexec performed quite well with my system (with no initrd stuff) when i was playing with it on early 2.6.0-testx love releases.
Reading Lovechild´s post, can it never be included again in love ?? I was hoping not read this...
Thanx! |
|
Back to top |
|
|
steel300 Veteran
Joined: 10 Jul 2003 Posts: 1155
|
Posted: Wed Feb 25, 2004 5:00 pm Post subject: |
|
|
gringo wrote: | Well, kexec performed quite well with my system (with no initrd stuff) when i was playing with it on early 2.6.0-testx love releases.
Reading Lovechild´s post, can it never be included again in love ?? I was hoping not read this...
Thanx! |
Kexec is too hard to patch in and make work right now. When it has matured a bit more, I'll put it back in. Right now, there are too many things fighting for syscalls. _________________ Rationality is the recognition of the fact that nothing can alter the truth and nothing can take precedence over that act of perceiving it. |
|
Back to top |
|
|
gringo Advocate
Joined: 27 Apr 2003 Posts: 3793
|
Posted: Wed Feb 25, 2004 5:32 pm Post subject: |
|
|
ok, thanx for your quick reply !
EDIT: did anyone of you guys played with this??
http://www.linux-vserver.org/
regards |
|
Back to top |
|
|
Evil Dark Archon Guru
Joined: 21 Dec 2002 Posts: 562 Location: Santa Rosa, CA
|
Posted: Wed Feb 25, 2004 7:32 pm Post subject: |
|
|
i've tried to but the ipvsadm that was in portage at the time and i've seen no indication of an update, doesn't seem to like 2.6 kernels. _________________ This post has been over explained for newb-informing purposes.
Registered Linux user 347334
Abit AV8-3rd eye, AMD Athlon64 3500+ 90nm, ATI Radeon x850 pro |
|
Back to top |
|
|
gringo Advocate
Joined: 27 Apr 2003 Posts: 3793
|
Posted: Wed Feb 25, 2004 8:17 pm Post subject: |
|
|
ok, will programm carnivore to listening to gentoos-ipvsadm changelog
thanx |
|
Back to top |
|
|
Master_Of_Disaster l33t
Joined: 28 Feb 2003 Posts: 610 Location: 15.05072° East, 48.13747° North (aka Mauer), Austria
|
|
Back to top |
|
|
steel300 Veteran
Joined: 10 Jul 2003 Posts: 1155
|
Posted: Wed Feb 25, 2004 8:55 pm Post subject: |
|
|
Master_Of_Disaster
I've tried compiling, but I can't seem to get it right. Every time I compile it goes back to the i386 includes. I'll try on a clean tree, and see how it goes. _________________ Rationality is the recognition of the fact that nothing can alter the truth and nothing can take precedence over that act of perceiving it. |
|
Back to top |
|
|
PrakashP Veteran
Joined: 27 Oct 2003 Posts: 1249 Location: C.C.A.A., Germania
|
Posted: Wed Feb 25, 2004 9:57 pm Post subject: |
|
|
@steel300
I think ther is no need to include the nforce_apic patch. If that is the one which puts the timer to apic, then this patch has been merged. Considering the disconnect issue, I *highly* recommend to try ross' latest patch with C1halt. Unfortunaltey it is not wel enough designed to include into love sources, but for people needing it, it seems to be the best option, so far.
I have noticed something about Nick's scheduler. I really think the default one is more smooth on my machine, as with the default one, I never get stuttering of my mouse, but with Nick's, I can eg. easily get a slight stutter, if I click a link in thunderbird and firefox opens a new tab for it. |
|
Back to top |
|
|
Spawn of Lovechild Apprentice
Joined: 03 Feb 2004 Posts: 253 Location: Århus, Denmark
|
Posted: Wed Feb 25, 2004 9:59 pm Post subject: |
|
|
PrakashKC wrote: | @steel300
I have noticed something about Nick's scheduler. I really think the default one is more smooth on my machine, as with the default one, I never get stuttering of my mouse, but with Nick's, I can eg. easily get a slight stutter, if I click a link in thunderbird and firefox opens a new tab for it. |
I'm of the same opinion atm. Nicks scheduler seems to handle combined IO and CPU load really badly on my machine. However X feels much smoother with X reniced to -10 on Nicks scheduler (like the doctor ordered) _________________ Proud to be a 22 year old Infidel, GNOME lover and member of LIK. |
|
Back to top |
|
|
PrakashP Veteran
Joined: 27 Oct 2003 Posts: 1249 Location: C.C.A.A., Germania
|
Posted: Wed Feb 25, 2004 10:11 pm Post subject: |
|
|
Unfortunately I don't see/feel much difference with X reniced. At which points do you specifically feel the difference? |
|
Back to top |
|
|
Spawn of Lovechild Apprentice
Joined: 03 Feb 2004 Posts: 253 Location: Århus, Denmark
|
Posted: Wed Feb 25, 2004 10:20 pm Post subject: |
|
|
PrakashKC wrote: | Unfortunately I don't see/feel much difference with X reniced. At which points do you specifically feel the difference? |
Mostly mouse smoothness, and redraw speed.
But the sad thing is that my machine completely stalls when I rip a cd to oggs, it grinds to a halt. _________________ Proud to be a 22 year old Infidel, GNOME lover and member of LIK. |
|
Back to top |
|
|
pestilence Apprentice
Joined: 05 Feb 2004 Posts: 213 Location: Athens / Greece
|
Posted: Wed Feb 25, 2004 10:58 pm Post subject: |
|
|
Once again outstanding...i got on the run the last few days...today my first query in the search field was love sources and wham r4 released...
My 5 cents to Steel the insane man with the tons of pizza burgains and the endless time and kindness of making this project work Its the first time after many years that i feel again what Linux is supposed to be...
Shall i order some Greek pizza? Man this kernel rockz! _________________ Gentoo the rising hope |
|
Back to top |
|
|
Evil Dark Archon Guru
Joined: 21 Dec 2002 Posts: 562 Location: Santa Rosa, CA
|
Posted: Wed Feb 25, 2004 11:33 pm Post subject: |
|
|
I haven't had any problems with either nick's scheduler or my nforce2 chipset. _________________ This post has been over explained for newb-informing purposes.
Registered Linux user 347334
Abit AV8-3rd eye, AMD Athlon64 3500+ 90nm, ATI Radeon x850 pro |
|
Back to top |
|
|
Master_Of_Disaster l33t
Joined: 28 Feb 2003 Posts: 610 Location: 15.05072° East, 48.13747° North (aka Mauer), Austria
|
Posted: Wed Feb 25, 2004 11:44 pm Post subject: |
|
|
@steel
I'd like to see these 3 patches in love-sources:
Beware, this patches were made by myself. I am using a kernel patched with these patches, it doesn't seem to break anything, but be warned though.
This fixes the "compound expressions as lvalues is deprecated" warning when compiling with GCC 3.4 on AMD64
Code: | $ cat gcc-3.4-rcupdate.h-warn-fix.patch
--- linux-2.6.3-love4/include/asm-x86_64/percpu.h 2004-02-23 19:47:55.000000000 +0100
+++ linux/include/asm-x86_64/percpu.h 2004-02-26 00:29:00.880523784 +0100
@@ -39,7 +39,7 @@
#define DEFINE_PER_CPU(type, name) \
__typeof__(type) per_cpu__##name
-#define per_cpu(var, cpu) ((void)cpu, per_cpu__##var)
+#define per_cpu(var, cpu) (*((void)cpu, &per_cpu__##var))
#define __get_cpu_var(var) per_cpu__##var
#endif /* SMP */ |
This one adds a parameter 'init' to the it87 module and turns off the register initialization on module load. I made this because it caused my shuttle's fan to switch to full speed. As this was used with older versions of lm_sensors apparantly no problems, I think it is safe to add this.
Code: | $ cat it87-shuttle-fix.patch
--- linux-2.6.3-mod1/drivers/i2c/chips/it87.c 2004-02-22 23:28:38.000000000 +0100
+++ linux/drivers/i2c/chips/it87.c 2004-02-06 12:23:37.000000000 +0100
@@ -57,6 +57,8 @@
/* Update battery voltage after every reading if true */
static int update_vbat = 0;
+/* Should the hardware be reset? */
+static int init = 0;
/* Enable Temp1 as thermal resistor */
/* Enable Temp2 as thermal diode */
@@ -830,59 +832,60 @@
{
/* Reset all except Watchdog values and last conversion values
This sets fan-divs to 2, among others */
- it87_write_value(client, IT87_REG_CONFIG, 0x80);
- it87_write_value(client, IT87_REG_VIN_MIN(0),
- IN_TO_REG(IT87_INIT_IN_MIN_0));
- it87_write_value(client, IT87_REG_VIN_MAX(0),
- IN_TO_REG(IT87_INIT_IN_MAX_0));
- it87_write_value(client, IT87_REG_VIN_MIN(1),
- IN_TO_REG(IT87_INIT_IN_MIN_1));
- it87_write_value(client, IT87_REG_VIN_MAX(1),
- IN_TO_REG(IT87_INIT_IN_MAX_1));
- it87_write_value(client, IT87_REG_VIN_MIN(2),
- IN_TO_REG(IT87_INIT_IN_MIN_2));
- it87_write_value(client, IT87_REG_VIN_MAX(2),
- IN_TO_REG(IT87_INIT_IN_MAX_2));
- it87_write_value(client, IT87_REG_VIN_MIN(3),
- IN_TO_REG(IT87_INIT_IN_MIN_3));
- it87_write_value(client, IT87_REG_VIN_MAX(3),
- IN_TO_REG(IT87_INIT_IN_MAX_3));
- it87_write_value(client, IT87_REG_VIN_MIN(4),
- IN_TO_REG(IT87_INIT_IN_MIN_4));
- it87_write_value(client, IT87_REG_VIN_MAX(4),
- IN_TO_REG(IT87_INIT_IN_MAX_4));
- it87_write_value(client, IT87_REG_VIN_MIN(5),
- IN_TO_REG(IT87_INIT_IN_MIN_5));
- it87_write_value(client, IT87_REG_VIN_MAX(5),
- IN_TO_REG(IT87_INIT_IN_MAX_5));
- it87_write_value(client, IT87_REG_VIN_MIN(6),
- IN_TO_REG(IT87_INIT_IN_MIN_6));
- it87_write_value(client, IT87_REG_VIN_MAX(6),
- IN_TO_REG(IT87_INIT_IN_MAX_6));
- it87_write_value(client, IT87_REG_VIN_MIN(7),
- IN_TO_REG(IT87_INIT_IN_MIN_7));
- it87_write_value(client, IT87_REG_VIN_MAX(7),
- IN_TO_REG(IT87_INIT_IN_MAX_7));
- /* Note: Battery voltage does not have limit registers */
- it87_write_value(client, IT87_REG_FAN_MIN(0),
- FAN_TO_REG(IT87_INIT_FAN_MIN_1, 2));
- it87_write_value(client, IT87_REG_FAN_MIN(1),
- FAN_TO_REG(IT87_INIT_FAN_MIN_2, 2));
- it87_write_value(client, IT87_REG_FAN_MIN(2),
- FAN_TO_REG(IT87_INIT_FAN_MIN_3, 2));
- it87_write_value(client, IT87_REG_TEMP_HIGH(0),
- TEMP_TO_REG(IT87_INIT_TEMP_HIGH_1));
- it87_write_value(client, IT87_REG_TEMP_LOW(0),
- TEMP_TO_REG(IT87_INIT_TEMP_LOW_1));
- it87_write_value(client, IT87_REG_TEMP_HIGH(1),
- TEMP_TO_REG(IT87_INIT_TEMP_HIGH_2));
- it87_write_value(client, IT87_REG_TEMP_LOW(1),
- TEMP_TO_REG(IT87_INIT_TEMP_LOW_2));
- it87_write_value(client, IT87_REG_TEMP_HIGH(2),
- TEMP_TO_REG(IT87_INIT_TEMP_HIGH_3));
- it87_write_value(client, IT87_REG_TEMP_LOW(2),
- TEMP_TO_REG(IT87_INIT_TEMP_LOW_3));
-
+ if (init==1) {
+ it87_write_value(client, IT87_REG_CONFIG, 0x80);
+ it87_write_value(client, IT87_REG_VIN_MIN(0),
+ IN_TO_REG(IT87_INIT_IN_MIN_0));
+ it87_write_value(client, IT87_REG_VIN_MAX(0),
+ IN_TO_REG(IT87_INIT_IN_MAX_0));
+ it87_write_value(client, IT87_REG_VIN_MIN(1),
+ IN_TO_REG(IT87_INIT_IN_MIN_1));
+ it87_write_value(client, IT87_REG_VIN_MAX(1),
+ IN_TO_REG(IT87_INIT_IN_MAX_1));
+ it87_write_value(client, IT87_REG_VIN_MIN(2),
+ IN_TO_REG(IT87_INIT_IN_MIN_2));
+ it87_write_value(client, IT87_REG_VIN_MAX(2),
+ IN_TO_REG(IT87_INIT_IN_MAX_2));
+ it87_write_value(client, IT87_REG_VIN_MIN(3),
+ IN_TO_REG(IT87_INIT_IN_MIN_3));
+ it87_write_value(client, IT87_REG_VIN_MAX(3),
+ IN_TO_REG(IT87_INIT_IN_MAX_3));
+ it87_write_value(client, IT87_REG_VIN_MIN(4),
+ IN_TO_REG(IT87_INIT_IN_MIN_4));
+ it87_write_value(client, IT87_REG_VIN_MAX(4),
+ IN_TO_REG(IT87_INIT_IN_MAX_4));
+ it87_write_value(client, IT87_REG_VIN_MIN(5),
+ IN_TO_REG(IT87_INIT_IN_MIN_5));
+ it87_write_value(client, IT87_REG_VIN_MAX(5),
+ IN_TO_REG(IT87_INIT_IN_MAX_5));
+ it87_write_value(client, IT87_REG_VIN_MIN(6),
+ IN_TO_REG(IT87_INIT_IN_MIN_6));
+ it87_write_value(client, IT87_REG_VIN_MAX(6),
+ IN_TO_REG(IT87_INIT_IN_MAX_6));
+ it87_write_value(client, IT87_REG_VIN_MIN(7),
+ IN_TO_REG(IT87_INIT_IN_MIN_7));
+ it87_write_value(client, IT87_REG_VIN_MAX(7),
+ IN_TO_REG(IT87_INIT_IN_MAX_7));
+ /* Note: Battery voltage does not have limit registers */
+ it87_write_value(client, IT87_REG_FAN_MIN(0),
+ FAN_TO_REG(IT87_INIT_FAN_MIN_1, 2));
+ it87_write_value(client, IT87_REG_FAN_MIN(1),
+ FAN_TO_REG(IT87_INIT_FAN_MIN_2, 2));
+ it87_write_value(client, IT87_REG_FAN_MIN(2),
+ FAN_TO_REG(IT87_INIT_FAN_MIN_3, 2));
+ it87_write_value(client, IT87_REG_TEMP_HIGH(0),
+ TEMP_TO_REG(IT87_INIT_TEMP_HIGH_1));
+ it87_write_value(client, IT87_REG_TEMP_LOW(0),
+ TEMP_TO_REG(IT87_INIT_TEMP_LOW_1));
+ it87_write_value(client, IT87_REG_TEMP_HIGH(1),
+ TEMP_TO_REG(IT87_INIT_TEMP_HIGH_2));
+ it87_write_value(client, IT87_REG_TEMP_LOW(1),
+ TEMP_TO_REG(IT87_INIT_TEMP_LOW_2));
+ it87_write_value(client, IT87_REG_TEMP_HIGH(2),
+ TEMP_TO_REG(IT87_INIT_TEMP_HIGH_3));
+ it87_write_value(client, IT87_REG_TEMP_LOW(2),
+ TEMP_TO_REG(IT87_INIT_TEMP_LOW_3));
+ }
/* Enable voltage monitors */
it87_write_value(client, IT87_REG_VIN_ENABLE, 0xff);
@@ -991,6 +994,8 @@
MODULE_PARM_DESC(update_vbat, "Update vbat if set else return powerup value");
MODULE_PARM(temp_type, "i");
MODULE_PARM_DESC(temp_type, "Temperature sensor type, normally leave unset");
+MODULE_PARM(init, "i");
+MODULE_PARM_DESC(init, "Reset hardware on load");
MODULE_LICENSE("GPL");
module_init(sm_it87_init); |
This one modifies the kernel's siimage module to support SiI 3512, the SCSI version didn't work for me.
Code: | # cat ~fuero/kernel/patches/patch-sii3512_support
diff -Naur linux-2.6.1/drivers/ide/pci/siimage.c linux/drivers/ide/pci/siimage.c
--- linux-2.6.1/drivers/ide/pci/siimage.c 2004-01-22 17:54:16.536108664 +0100
+++ linux/drivers/ide/pci/siimage.c 2004-01-22 17:50:03.564566184 +0100
@@ -55,6 +55,7 @@
switch(pdev->device)
{
case PCI_DEVICE_ID_SII_3112:
+ case PCI_DEVICE_ID_SII_3512:
case PCI_DEVICE_ID_SII_1210SA:
return 1;
case PCI_DEVICE_ID_SII_680:
@@ -1197,6 +1198,7 @@
{ PCI_VENDOR_ID_CMD, PCI_DEVICE_ID_SII_680, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
{ PCI_VENDOR_ID_CMD, PCI_DEVICE_ID_SII_3112, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 1},
{ PCI_VENDOR_ID_CMD, PCI_DEVICE_ID_SII_1210SA, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 2},
+ { PCI_VENDOR_ID_CMD, PCI_DEVICE_ID_SII_3512, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 3},
{ 0, },
};
diff -Naur linux-2.6.1/drivers/ide/pci/siimage.h linux/drivers/ide/pci/siimage.h
--- linux-2.6.1/drivers/ide/pci/siimage.h 2004-01-09 07:59:43.000000000 +0100
+++ linux/drivers/ide/pci/siimage.h 2004-01-22 17:51:00.554902336 +0100
@@ -82,6 +82,19 @@
.enablebits = {{0x00,0x00,0x00}, {0x00,0x00,0x00}},
.bootable = ON_BOARD,
.extra = 0,
+ },{ /* 3 */
+ .vendor = PCI_VENDOR_ID_CMD,
+ .device = PCI_DEVICE_ID_SII_3512,
+ .name = "SiI3512 Serial ATA",
+ .init_chipset = init_chipset_siimage,
+ .init_iops = init_iops_siimage,
+ .init_hwif = init_hwif_siimage,
+ .channels = 2,
+ .autodma = AUTODMA,
+ .enablebits = {{0x00,0x00,0x00}, {0x00,0x00,0x00}},
+ .bootable = ON_BOARD,
+ .extra = 0,
+
},{
.vendor = 0,
.device = 0,
diff -Naur linux-2.6.1/include/linux/pci_ids.h linux/include/linux/pci_ids.h
--- linux-2.6.1/include/linux/pci_ids.h 2004-01-22 17:54:16.969042848 +0100
+++ linux/include/linux/pci_ids.h 2004-01-22 17:51:27.574794688 +0100
@@ -887,6 +887,7 @@
#define PCI_DEVICE_ID_SII_680 0x0680
#define PCI_DEVICE_ID_SII_3112 0x3112
+#define PCI_DEVICE_ID_SII_3512 0x3512
#define PCI_DEVICE_ID_SII_1210SA 0x0240
#define PCI_VENDOR_ID_VISION 0x1098 |
Applying the patches to 2.6.3-love4:
Code: | hephaestos linux-2.6.3-love4 # cat ~fuero/kernel/patches/gcc-3.4-rcupdate.h-warn-fix.patch | patch -p1 --dry-run
patching file include/asm-x86_64/percpu.h
hephaestos linux-2.6.3-love4 # cat ~fuero/kernel/patches/patch-sii3512_support | patch -p1 --dry-run
patching file drivers/ide/pci/siimage.c
patching file drivers/ide/pci/siimage.h
Hunk #1 succeeded at 62 (offset -20 lines).
patching file include/linux/pci_ids.h
Hunk #1 succeeded at 901 (offset 14 lines).
hephaestos linux-2.6.3-love4 # cat ~fuero/kernel/patches/it87-shuttle-fix.patch | patch -p1 --dry-run
patching file drivers/i2c/chips/it87.c |
_________________ post tenebras lux, post fenestras tux
Registered Linux User Nr. 312509
Adopt an unanswered post today! |
|
Back to top |
|
|
steel300 Veteran
Joined: 10 Jul 2003 Posts: 1155
|
Posted: Wed Feb 25, 2004 11:56 pm Post subject: |
|
|
Master_Of_Disaster:
Those patches look good, could you email them to me at
jpcox at iastate dot edu _________________ Rationality is the recognition of the fact that nothing can alter the truth and nothing can take precedence over that act of perceiving it. |
|
Back to top |
|
|
neonik Guru
Joined: 08 Oct 2003 Posts: 501
|
Posted: Thu Feb 26, 2004 12:24 am Post subject: |
|
|
Using 2.6.3-love4, has anyone noticed an increased memory consumption compared to 2.6.2 or 2.6.1? I've got an about 100-200 higher memory usage than in 2.6.1 and 2.6.2-rc2. But this is not an issue of love-sources or mm-sources, it's an issue with vanilla too. _________________ Best regards,
neonik
netshot-0.0.8 - script that takes screenshots, generates their thumbnails and uploads them all! (has not been updated). |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|