All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Cc: Gediminas Simanskis <gediminas@8devices.com>,
	Bernd Krumboeck <krumboeck@universalnet.at>
Subject: [SOLVED] Re: usb_8dev: Initialisation issue with powered USB 2.0 hub
Date: Fri, 13 Nov 2015 21:20:36 +0100	[thread overview]
Message-ID: <56464614.9000201@hartkopp.net> (raw)
In-Reply-To: <54EEEA4C.80009@hartkopp.net>

Hi all,

the issue discussed in this thread has been fixed by Gediminas.

The new firmware can be found at
http://www.8devices.com/usb2can

http://www.8devices.com/media/files/usb2can_1_7.zip

The firmware sources have been updated too:
https://github.com/krumboeck/usb2can_firmware

Many thanks,
Oliver


On 26.02.2015 10:41, Oliver Hartkopp wrote:
> Hello Gediminas,
>
>> On 16.02.2015 18:12, Gediminas Simanskis wrote:
>>
>>> IMHO in main firmware cycle need to check lower USB protocol library states.
>>> Currently firmware after descriptor initialization goes to infinite loop and
>>> don't check lower USB layer states anymore.
>
> As you already named the potential issue: When do you plan to release a new
> firmware that fixes this warmstart problem?
>
> Regards,
> Oliver
>



      reply	other threads:[~2015-11-13 20:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05 18:03 usb_8dev: Initialisation issue with powered USB 2.0 hub Oliver Hartkopp
2015-02-09 19:30 ` Bernd Krumboeck
2015-02-09 19:38   ` Oliver Hartkopp
2015-02-14  8:17     ` Bernd Krumboeck
2015-02-16  6:36       ` Oliver Hartkopp
2015-02-16 17:12         ` Gediminas Simanskis
2015-02-17  6:19           ` Oliver Hartkopp
2015-02-17 10:51             ` Gediminas Simanskis
2015-02-17 18:15               ` Bernd Krumboeck
2015-02-26  9:41             ` Oliver Hartkopp
2015-11-13 20:20               ` Oliver Hartkopp [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=56464614.9000201@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=gediminas@8devices.com \
    --cc=krumboeck@universalnet.at \
    --cc=linux-can@vger.kernel.org \
    /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.