From: Johan Hovold <johan@kernel.org>
To: Doug Goldstein <cardoe@cardoe.com>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] USB: ftdi_sio: Use jtag quirk for SNAP Connect E10
Date: Wed, 25 Mar 2015 15:31:09 +0100 [thread overview]
Message-ID: <20150325143109.GD10412@localhost> (raw)
In-Reply-To: <CAFWqQMT3=819YGv6qGLVjXdveSHBTgfGVVe4zO87_Wrkxwaw8w@mail.gmail.com>
On Wed, Mar 25, 2015 at 08:51:26AM -0500, Doug Goldstein wrote:
> On Wed, Mar 25, 2015 at 3:44 AM, Johan Hovold <johan@kernel.org> wrote:
> > On Mon, Mar 23, 2015 at 08:34:48PM -0500, Doug Goldstein wrote:
> >> This patch uses the existing CALAO Systems ftdi_8u2232c_probe in order
> >> to avoid attaching a TTY to the JTAG port as this board is based on the
> >> CALAO Systems reference design and needs the same fix up.
> >
> > Thanks for the patch. Could you please provide the full "lsusb -v"
> > output for the device before I apply it?
> This is the "lsusb -v" of the device in question.
Thanks for the info.
> I'm game for a better way of avoiding having a tty bound to the first
> interface. I've been trying to figure out if I can do it via udev as
> well but have had no luck there.
I'm afraid there's not much else we can do as long as people keep
reusing the default chip IDs.
Patch now applied after I cleaned up the existing logic somewhat.
Thanks,
Johan
prev parent reply other threads:[~2015-03-25 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 1:34 [PATCH] USB: ftdi_sio: Use jtag quirk for SNAP Connect E10 Doug Goldstein
2015-03-25 8:44 ` Johan Hovold
2015-03-25 13:51 ` Doug Goldstein
2015-03-25 14:31 ` Johan Hovold [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=20150325143109.GD10412@localhost \
--to=johan@kernel.org \
--cc=cardoe@cardoe.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@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.