Hi Linus,
please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git release
This will restore the ACPI_DOCK driver, plus other fixes below.
thanks!
-Len
ps. a plain patch is also available here:
ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/rele
[adding linux-acpi@vger.kernel.org to cc]
acpi=off used to be handled by acpi_bus_register_driver()
for these drivers.
But now acpi_lock_ac_dir() and acpi_lock_battery_dir()
for procfs are inserted before that in the _init functions.
This will be a problem for sbs.c also.
Vladimir,
Any reason t
Okay, if system_state is off limits, there here is what I've got
(interesting part is the last 20 lines)
ACPI: acpi_os_allocate() fixes
Replace acpi_in_resume with a more general hack
to check irqs_disabled() on any kmalloc() from ACPI.
While setting (system_state != SYSTEM_RUNNING) on resume
see
On Sun, 09 Jul 2006 23:22:14 +1200 Reuben Farrelly wrote:
> 2. Onto some more minor warnings:
>
> ACPI: bus type pci registered
> PCI: BIOS Bug: MCFG area at f000 is not E820-reserved
> PCI: Not using MMCONFIG.
> PCI: Using configuration type 1
Yes, I have all of those.
> ACPI: Interpreter
Can anyone give me a hint on how to fix this? Anything would be useful.
>Hi. I'm a newbie to linux, but I've been getting this problem ever
>since I installed it on my computer (I've already tested Fedora Core 5
>and Ubuntu 6, both having the same problem).
>
>1) I first discovered that my lapto
>Hi. I'm a newbie to linux, but I've been getting this problem ever
>since I installed it on my computer (I've already tested Fedora Core 5
>and Ubuntu 6, both having the same problem).
>
>1) I first discovered that my laptop display didn't turn off when the
>lid was closed (I can tell because I c
On Saturday 08 July 2006 16:24, [EMAIL PROTECTED] wrote:
> I recently thought about using coldplug (/etc/hotplug/*.rc) scripts to
> automagically load modules responsible for ACPI-controlled devices such
> as button, battery, laptop extras. To accomplish this I wrote a trivial
> kernel patch whi
applied.
thanks,
-Len
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Sent: Friday, July 07, 2006 2:53 AM
>To: Brown, Len
>Cc: linux-acpi@vger.kernel.org; [EMAIL PROTECTED];
>[EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: [patch 5/5] acpi: initialise cm_sbs_sem
>Default is 'n' when omitted...
This default stuff seems to be make-work
without any real value.
At one time we had default =m to try to show
what a reasonable usable configuration was.
These got globally replaced to =y because
apparently it is taboo to have default =m.
But =y defaults don't ma
I see I get no response, where should I go to get some help on this issue?
If I have to fix it by myself, could you give me some hint on where to start?
On 7/9/06, Ruslán Ledesma Garza <[EMAIL PROTECTED]> wrote:
>From: "Ruslán Ledesma Garza" <[EMAIL PROTECTED]>
>To: "Ruslán Ledesma Garza" <[
On Monday 10 July 2006 04:27, Brown, Len wrote:
> I don't see this upstream, so I applied it to my tree.
Linus dropped the last batch. I resent it.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
NAK,
this patch hides, rather than fixes the issue.
-Len
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Sent: Friday, July 07, 2006 2:53 AM
>To: Brown, Len
>Cc: linux-acpi@vger.kernel.org; [EMAIL PROTECTED]; Starikovskiy,
>Alexey Y; [EMAIL PROTECTED]; [EMAIL PR
On Sun, 9 Jul 2006 22:19:28 -0400 Brown, Len wrote:
> While SBS is rare in the general population,
> it is common on some product lines, and thus
> this should have the same default as the regular
> battery driver.
>
> Rahter than y or n, neither should have any default --
> I'll fix that now.
D
I don't see this upstream, so I applied it to my tree.
thanks,
-Len
>-Original Message-
>From: Andi Kleen [mailto:[EMAIL PROTECTED]
>Sent: Thursday, July 06, 2006 12:14 PM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
>linux-acpi@vger.kernel.org; Brown, Len
>Subject
While SBS is rare in the general population,
it is common on some product lines, and thus
this should have the same default as the regular
battery driver.
Rahter than y or n, neither should have any default --
I'll fix that now.
thanks,
-Len
>-Original Message-
>From: [EMAIL PROTECTED]
>it allows the illegal configuration
>ACPI_IBM_DOCK=y, HOTPLUG_PCI_ACPI=y/m, ACPI_DOCK=y/m.
Hmm, that seems to be an additional pre-existing problem.
Since ACPI_IBM_DOCK is going away, lets put the burden
of depending on ACPI_DOCK=n on it, rather than the reverse.
Lets not use select, since it ba
On Mon, 10 Jul 2006, Adrian Bunk wrote:
>
> This patch looks wrong since it allows the illegal configuration
> ACPI_IBM_DOCK=y, HOTPLUG_PCI_ACPI=y/m, ACPI_DOCK=y/m.
Len?
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [E
From: "Ruslán Ledesma Garza" <[EMAIL PROTECTED]>
To: "Ruslán Ledesma Garza" <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED], linux-acpi@vger.kernel.org
Subject: Re: ACPI not working on DELL Inspiron 1150
Date: Sun, 9 Jul 2006 20:30:07 -0500
On 7/9/06, Ruslán Ledesma Garza <[EMAIL PROTECTED]> wrote:
On 7/9/06, Ruslán Ledesma Garza <[EMAIL PROTECTED]> wrote:
>From: "Brown, Len" <[EMAIL PROTECTED]>
>To: Ruslán Ledesma Garza
><[EMAIL PROTECTED]>,
>Subject: RE: ACPI not working on DELL Inspiron 1150
>Date: Sun, 9 Jul 2006 17:10:45 -0400
>
>
> >Hi. I'm a newbie to linux, but I've been getting
Hi.
On Monday 10 July 2006 08:38, Linus Torvalds wrote:
> On Sun, 9 Jul 2006, Brown, Len wrote:
> > So I ask you. If I fix the Kconfig issue today, will you accept
> > a push that restores this driver to 2.6.18?
>
> Sure.
Great! Sorry Linus from me too - I've been assigned to watch this for Redh
On Sun, Jul 09, 2006 at 07:03:23PM -0400, Brown, Len wrote:
>
> >It would be a solution to let HOTPLUG_PCI_ACPI depend on
> >(ACPI_DOCK || ACPI_DOCK=n), or the #if in
> >include/acpi/acpi_drivers.h could be changed to
> >#if defined(CONFIG_ACPI_DOCK) ||
> >(defined(CONFIG_ACPI_DOCK_MODULE) && de
fixed typo -- can't cook and type at the same time...
DOCKHPA
n n builds
n y -> y,y
n m -> m,m
y n builds
y y builds
y m builds
m n builds
m y -> y,y (previous note had typo, m,y)
m m bu
>It would be a solution to let HOTPLUG_PCI_ACPI depend on
>(ACPI_DOCK || ACPI_DOCK=n), or the #if in
>include/acpi/acpi_drivers.h could be changed to
>#if defined(CONFIG_ACPI_DOCK) ||
>(defined(CONFIG_ACPI_DOCK_MODULE) && defined(MODULE))
CONFIG_HOTPLUG_PCI_ACPI requires CONFIG_ACPI_DOCK.
There
On Sun, 9 Jul 2006, Brown, Len wrote:
>
> So I ask you. If I fix the Kconfig issue today, will you accept
> a push that restores this driver to 2.6.18?
Sure.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTEC
>> >Fair enough. Reverted.
>>
>> I disagree with this decision, and would like to know what
>> is necessary to reverse it.
>
>Mistakes happen. Fair enough. They happen all the time. This
>time around, for the 2.6.18-rc1 thing, I had heard more than
>the usual "nobody even reacted", as Andrew had
From: "Brown, Len" <[EMAIL PROTECTED]>
To: Ruslán Ledesma Garza
<[EMAIL PROTECTED]>,
Subject: RE: ACPI not working on DELL Inspiron 1150
Date: Sun, 9 Jul 2006 17:10:45 -0400
>Hi. I'm a newbie to linux, but I've been getting this problem ever
>since I installed it on my computer (I've alrea
On Sun, 9 Jul 2006, Brown, Len wrote:
> >
> >Fair enough. Reverted.
>
> I disagree with this decision, and would like to know what
> is necessary to reverse it.
Mistakes happen. Fair enough. They happen all the time. This time around,
for the 2.6.18-rc1 thing, I had heard more than the usual "
On Sun, 9 Jul 2006 10:33:12 -0700
"Randy.Dunlap" <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] ~]# cat /proc/interrupts
> > CPU0 CPU1
> >0: 258266 0 IO-APIC-edge timer
> >4:355 0 IO-APIC-edge serial
> >6: 5
>>but I wonder
>>if the fact that my DST says "MSFT" could be the cause of ACPI not
>>working propertly.
>
>:-) This means it was built with the MSFT ASL compiler. Sometimes
>that is an issue, but we try to handle those issues and re-building
>the firmwarwe with Intel's compiler is okay for deb
>Hi. I'm a newbie to linux, but I've been getting this problem ever
>since I installed it on my computer (I've already tested Fedora Core 5
>and Ubuntu 6, both having the same problem).
>
>1) I first discovered that my laptop display didn't turn off when the
>lid was closed (I can tell because I c
On Sun, 2006-07-09 at 05:22 -0700, Andrew Morton wrote:
> On Sun, 09 Jul 2006 23:22:14 +1200
> Reuben Farrelly <[EMAIL PROTECTED]> wrote:
> > Note also the message midway through about losing some ticks, which if I
> > recall
> > correctly is not new to this -mm release. I'm not sure who to cc a
Hi. I'm a newbie to linux, but I've been getting this problem ever
since I installed it on my computer (I've already tested Fedora Core 5
and Ubuntu 6, both having the same problem).
1) I first discovered that my laptop display didn't turn off when the
lid was closed (I can tell because I can see
ACPICA 20060707 is now in the git tree on the test branch
and in the kernel.org test patch.
A couple of tweaks since Friday related to build warnings
from acpi_os_get_thread_id() returning a pointer and not an integer.
plus some changes in evxface.c to fix a build error and delete
some needless te
>If you address me directly when you are asking me to do something,
>that would really help me help you.
oops, I see you did this -- looks like I've got some snags in my mail
sorter.
-Len
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL
>> Two weeks ago, we had:
>> - a bug report
>> - a detailed description how to possibly fix this issue
>>
>> What we did NOT have was:
>> - any reaction by the patch author or any maintainer
>> (although with the exception of Linus, the recipients of
>the problem
>>description were exactly
On Sun, Jul 09, 2006 at 05:22:52AM -0700, Andrew Morton wrote:
> > ACPI: bus type pci registered
> > PCI: BIOS Bug: MCFG area at f000 is not E820-reserved
> > PCI: Not using MMCONFIG.
> > PCI: Using configuration type 1
> > ACPI: Interpreter enabled
> >
> > Is there any way to verify that ther
>> For the files that Linux gets from ACPICA, this diff shows how Linux
>> has diverged from upstream.
>>
>> acpica-unix-20060707.audit.diff:# 42 files changed, 211
>insertions(+), 92 deletions(-)
>
>300+ lines in 42 files. That doesn't look huge,
>but then I'm not trying to maintain it.
It isn
On Fri, 7 Jul 2006 20:57:27 -0400 Len Brown wrote:
> For the files that Linux gets from ACPICA, this diff shows how Linux
> has diverged from upstream.
>
> acpica-unix-20060707.audit.diff:# 42 files changed, 211 insertions(+), 92
> deletions(-)
300+ lines in 42 files. That doesn't look huge,
b
>> 2. Onto some more minor warnings:
>>
>> ACPI: bus type pci registered
>> PCI: BIOS Bug: MCFG area at f000 is not E820-reserved
>> PCI: Not using MMCONFIG.
>> PCI: Using configuration type 1
>> ACPI: Interpreter enabled
>>
>> Is there any way to verify that there really is a BIOS bug
>ther
On Sun, 09 Jul 2006 23:22:14 +1200 Reuben Farrelly wrote:
> On 9/07/2006 9:11 p.m., Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> >
> > - We're getting a relatively large number of crash reports coming out of the
> > core sys
Alan Cox wrote:
The old drivers/ide code uses much longer delays than the spec for some
ATAPI commands, and it looks as if there is a good reason for doing
so ...
FWIW, the code that ATADRVR (http://www.ata-atapi.com/) uses to issue
commands does something like
write Command registe
On Sun, 9 Jul 2006, Adrian Bunk wrote:
>
> Two weeks ago, we had:
> - a bug report
> - a detailed description how to possibly fix this issue
>
> What we did NOT have was:
> - any reaction by the patch author or any maintainer
> (although with the exception of Linus, the recipients of the prob
On 10/07/2006 12:56 a.m., Alan Cox wrote:
Ar Sul, 2006-07-09 am 05:22 -0700, ysgrifennodd Andrew Morton:
ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x30B0 irq 14
scsi4 : ata_piix
ata5.00: ATAPI, max UDMA/66
ata5.00: configured for UDMA/66
More ATAPI devices getting uppity about mode set
Ar Sul, 2006-07-09 am 05:22 -0700, ysgrifennodd Andrew Morton:
> > ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x30B0 irq 14
> > scsi4 : ata_piix
> > ata5.00: ATAPI, max UDMA/66
> > ata5.00: configured for UDMA/66
More ATAPI devices getting uppity about mode setting.
> John stuff. I suspec
On Sun, 09 Jul 2006 23:22:14 +1200
Reuben Farrelly <[EMAIL PROTECTED]> wrote:
>
>
> On 9/07/2006 9:11 p.m., Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> >
> > - We're getting a relatively large number of crash reports coming
On 9/07/2006 9:11 p.m., Andrew Morton wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
- We're getting a relatively large number of crash reports coming out of the
core sysfs/kobject/driver/bus code, and they're all really hard to diagnose.
I
46 matches
Mail list logo
