From: Bjorn Helgaas <bhelgaas@google.com>
To: Stephane Grosjean <s.grosjean@peak-system.com>
Cc: linux-acpi@vger.kernel.org, support@peak-system.com,
Robert Hancock <hancockrwd@gmail.com>,
linux-pci@vger.kernel.org
Subject: Re: Info about ACPI/PCI vs ISA
Date: Fri, 26 Oct 2012 03:31:44 -0600 [thread overview]
Message-ID: <CAErSpo4GFn_xSzMb7Y8cR+oJUT4LPi046zJs5iLUY0cp2c85zQ@mail.gmail.com> (raw)
In-Reply-To: <508A544F.1030007@peak-system.com>
On Fri, Oct 26, 2012 at 3:13 AM, Stephane Grosjean
<s.grosjean@peak-system.com> wrote:
> Hi Bjorn,
>
> Thanks for your answer. See my comments below...
>
> Le 26/10/2012 10:29, Bjorn Helgaas a écrit :
>>
>> On Wed, Sep 26, 2012 at 2:19 AM, Stephane Grosjean
>> <s.grosjean@peak-system.com> wrote:
>>
>>> I'm working on an issue with one of our PCI adapters.
>>> This PCI adapter is a standard and well proven board, for many years:
>>>
>>> $ lspci -v
>>> ...
>>> 04:08.0 Network controller: PEAK-System Technik GmbH PCAN-PCI CAN-Bus
>>> controller (rev 02)
>>> Subsystem: PEAK-System Technik GmbH 2 Channel CAN Bus SJC1000
>>> Flags: medium devsel, IRQ 11
>>> Memory at f0410000 (32-bit, non-prefetchable) [size=64K]
>>> Memory at f0400000 (32-bit, non-prefetchable) [size=64K]
>>> Kernel driver in use: pcan
>>>
>>>
>> Where's the source for the "pcan" driver? I see the pcan_usb driver
>> in the tree, but that looks like something different from what you're
>> looking at here.
>
>
> The "pcan" driver is an out-ot-tree driver which offers a chardev interface,
> not a mainline driver. The "pcan_usb" (as well as peak_pci...) are our
> recent linux-can (only) drivers.
> Since the "pcan" driver does exist since the old ages of 2.4 kernels, we
> need to continue to support it. See also below for more information about
> that...
>
>> Does the device work under any version of Linux? If so, please
>> collect the complete dmesg log from the newest working version, and
>> the same log from the broken version.
>
>
> Yes it does! Anyway, you'll find the complete dmesg.txt attached to that
> e-mail. Hoping this could help.
Thanks. You attached the log for the broken version. Can you also
attach a log from the newest working version of Linux?
I assume the same driver works on the old version but fails on new
versions. If so, it sounds like this might be a Linux regression, and
finding the newest working and oldest broken versions will help
identify it.
>>> - why does the system not succeed to "derive" routing for INTA? And why
>>> us?
>>
>> The derivation is based on ACPI _PRT tables. Regrettably, we don't
>> dump the _PRT contents in dmesg, so we'd need an acpidump to look
>> further into that.
>
> Well unfortunately, we are not able to provide this kind of information at
> this moment.
The acpidump isn't secret (it's not part of the BIOS source); it's
just information extracted from the running system. See
https://lesswatts.org/projects/acpi/utilities.php for details.
Bjorn
next prev parent reply other threads:[~2012-10-26 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 8:19 Info about ACPI/PCI vs ISA Stephane Grosjean
2012-10-26 4:44 ` Robert Hancock
2012-10-26 8:29 ` Bjorn Helgaas
2012-10-26 9:13 ` Stephane Grosjean
2012-10-26 9:31 ` Bjorn Helgaas [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-24 12:13 Stephane Grosjean
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAErSpo4GFn_xSzMb7Y8cR+oJUT4LPi046zJs5iLUY0cp2c85zQ@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=hancockrwd@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=s.grosjean@peak-system.com \
--cc=support@peak-system.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).