Regarding the thread accessible at:
http://groups.google.com/group/linux.kernel/browse_frm/thread/bdc8fd08fb601c26
that ended with "looks like it is specific to your hardware",
Can I check where we are with this?
I've just had a small installation run fail on 3 boxes with the same
problems,
Regarding the thread accessible at:
http://groups.google.com/group/linux.kernel/browse_frm/thread/bdc8fd08fb601c26
that ended with looks like it is specific to your hardware,
Can I check where we are with this?
I've just had a small installation run fail on 3 boxes with the same
problems,
John wrote:
> Jesse Brandeburg wrote:
>> What would you like to do? At this stage I would like e100 to work
>> better than it is, but I'm not sure what to do next.
>
> Hello everyone,
>
> I'm resurrecting this thread because it appears we'll need to support
> these motherboards for several
John wrote:
Jesse Brandeburg wrote:
What would you like to do? At this stage I would like e100 to work
better than it is, but I'm not sure what to do next.
Hello everyone,
I'm resurrecting this thread because it appears we'll need to support
these motherboards for several months to
Jesse Brandeburg wrote:
John wrote:
Jesse Brandeburg wrote:
can you try adding mdelay(100); in e100_eeprom_load before the for loop,
and then change the multiple udelay(4) to mdelay(1) in e100_eeprom_read
I applied the attached patch.
Loading the driver now takes around one minute :-)
Jesse Brandeburg wrote:
John wrote:
Jesse Brandeburg wrote:
can you try adding mdelay(100); in e100_eeprom_load before the for loop,
and then change the multiple udelay(4) to mdelay(1) in e100_eeprom_read
I applied the attached patch.
Loading the driver now takes around one minute :-)
On 12/1/06, John <[EMAIL PROTECTED]> wrote:
> can you try adding mdelay(100); in e100_eeprom_load before the for loop,
> and then change the multiple udelay(4) to mdelay(1) in e100_eeprom_read
I applied the attached patch.
Loading the driver now takes around one minute :-)
ouch, but yep,
On 12/1/06, John [EMAIL PROTECTED] wrote:
can you try adding mdelay(100); in e100_eeprom_load before the for loop,
and then change the multiple udelay(4) to mdelay(1) in e100_eeprom_read
I applied the attached patch.
Loading the driver now takes around one minute :-)
ouch, but yep, thats
On 11/29/06, John <[EMAIL PROTECTED]> wrote:
> Let's go ahead and print the output from e100_load_eeprom
> debug patch attached.
Loading (then unloading) e100.ko fails the first few times (i.e. the
driver claims one of the EEPROMs is corrupted). Thereafter, sometimes it
fails, other times it
Jesse Brandeburg wrote:
John wrote:
Here is some context for those who have been added to the CC list:
http://groups.google.com/group/linux.kernel/browse_frm/thread/bdc8fd08fb601c26
As far as I understand, some consider the eepro100 driver to be
obsolete, and it has been considered for
Jesse Brandeburg wrote:
John wrote:
Here is some context for those who have been added to the CC list:
http://groups.google.com/group/linux.kernel/browse_frm/thread/bdc8fd08fb601c26
As far as I understand, some consider the eepro100 driver to be
obsolete, and it has been considered for
On 11/29/06, John [EMAIL PROTECTED] wrote:
Let's go ahead and print the output from e100_load_eeprom
debug patch attached.
Loading (then unloading) e100.ko fails the first few times (i.e. the
driver claims one of the EEPROMs is corrupted). Thereafter, sometimes it
fails, other times it works.
On 11/27/06, John <[EMAIL PROTECTED]> wrote:
John wrote:
>> -0009 : System RAM
>> 000a-000b : Video RAM area
>> 000f-000f : System ROM
>> 0010-0ffe : System RAM
>> 0010-00296a1a : Kernel code
>> 00296a1b-0031bbe7 : Kernel data
>> 0fff-0fff2fff :
John wrote:
-0009 : System RAM
000a-000b : Video RAM area
000f-000f : System ROM
0010-0ffe : System RAM
0010-00296a1a : Kernel code
00296a1b-0031bbe7 : Kernel data
0fff-0fff2fff : ACPI Non-volatile Storage
0fff3000-0fff : ACPI Tables
John wrote:
-0009 : System RAM
000a-000b : Video RAM area
000f-000f : System ROM
0010-0ffe : System RAM
0010-00296a1a : Kernel code
00296a1b-0031bbe7 : Kernel data
0fff-0fff2fff : ACPI Non-volatile Storage
0fff3000-0fff : ACPI Tables
On 11/27/06, John [EMAIL PROTECTED] wrote:
John wrote:
-0009 : System RAM
000a-000b : Video RAM area
000f-000f : System ROM
0010-0ffe : System RAM
0010-00296a1a : Kernel code
00296a1b-0031bbe7 : Kernel data
0fff-0fff2fff : ACPI Non-volatile
16 matches
Mail list logo
