All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephane Grosjean <s.grosjean@peak-system.com>
To: Oliver Hartkopp <oliver.hartkopp@volkswagen.de>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Testing peak_pci v6.1 / peak_usb v6 / peak_pcmcia v4.1
Date: Thu, 23 Feb 2012 16:00:31 +0100	[thread overview]
Message-ID: <4F46548F.7050300@peak-system.com> (raw)
In-Reply-To: <4F4642AA.9060103@volkswagen.de>

Hi Oliver,

Le 23/02/2012 14:44, Oliver Hartkopp a écrit :
> Hello Stephane,
>
> you can add to all these drivers
>
> - peak_pci v6.1 (http://marc.info/?l=linux-can&m=132973636320107&w=2)
> - peak_usb v6 (http://marc.info/?l=linux-can&m=132998590401560&w=2)
> - peak_pcmcia v4.1 (http://marc.info/?l=linux-pcmcia&m=132938721324159&w=2)
>
> my
>
> Tested-by: Oliver Hartkopp<socketcan@hartkopp.net>

Thanks for all of your precious time.

> Just two nitpicks:
>
> When having traffic the LEDs from the PCIeC are flashing faster than the PCMCIA LEDs.
> With no traffic and interface is up, they are flashing with the same frequency.

... I should check whether the two boards use the same chip to control 
the LEDs... But I think that the word "nitpicks" was especially invented 
for that particular issue ;-)

> The other one:
>
> usb 2-2: new high-speed USB device number 4 using ehci_hcd
> usb 2-2: config 1 interface 0 altsetting 0 bulk endpoint 0x83 has invalid maxpacket 64
> usb 2-2: config 1 interface 1 altsetting 0 bulk endpoint 0x86 has invalid maxpacket 64
> peak_usb 2-2:1.0: PEAK-System PCAN-USB Pro hwrev 0 serial FFFFFFFF.00000001 (2 channels)
> peak_usb 2-2:1.0: can4: attached to PCAN-USB Pro channel 0 (device 1)
> peak_usb 2-2:1.0: can5: attached to PCAN-USB Pro channel 1 (device 0)
> usbcore: registered new interface driver peak_usb
>
> Do you have any idea what
>
> "altsetting 0 bulk endpoint 0x83 has invalid maxpacket 64"
>
> means?
>
> Is this something that's caused by your driver or it is caused by the
> hardware configuration of the USBpro adapter? I assume it's the latter.

Yes you're right. These msgs are printed by the usb-core, before the 
_probe() function of the driver is called. It is something I will send 
back to our hw team...

> Regards,
> Oliver
>


Best regards,

Stéphane

--
PEAK-System Technik GmbH, Otto-Roehm-Strasse 69, D-64293 Darmstadt 
Geschaeftsleitung: A.Gach/U.Wilhelm,St.Nr.:007/241/13586 FA Darmstadt 
HRB-9183 Darmstadt, Ust.IdNr.:DE 202220078, WEE-Reg.-Nr.: DE39305391 
Tel.+49 (0)6151-817320 / Fax:+49 (0)6151-817329, info@peak-system.com

      reply	other threads:[~2012-02-23 15:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22  8:59 About peak_pci PATCH v6.1 Stephane Grosjean
2012-02-22 16:03 ` Oliver Hartkopp
2012-02-23 13:44   ` Testing peak_pci v6.1 / peak_usb v6 / peak_pcmcia v4.1 Oliver Hartkopp
2012-02-23 15:00     ` Stephane Grosjean [this message]

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=4F46548F.7050300@peak-system.com \
    --to=s.grosjean@peak-system.com \
    --cc=linux-can@vger.kernel.org \
    --cc=oliver.hartkopp@volkswagen.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.