From: "Little, Jack" <jack.tay.little@hpe.com>
To: "Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Desimone, Ashley E" <ashley.e.desimone@intel.com>
Subject: Re: FtdiUsbSerialDxe
Date: Thu, 27 May 2021 16:25:42 +0000 [thread overview]
Message-ID: <TU4PR8401MB0862B8C337F7DE89E86B4E6FAB239@TU4PR8401MB0862.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <MWHPR1101MB21602114206FBFCA9CC21661CD239@MWHPR1101MB2160.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2653 bytes --]
You may be right, I've seen that the EFI_DEVICE_ERROR comes from UsbIoControlTransfer() where there is a conflict between the data length requested vs. received.
Thanks,
Jack
From: Desimone, Nathaniel L <nathaniel.l.desimone@intel.com>
Sent: Thursday, May 27, 2021 11:06 AM
To: Little, Jack <jack.tay.little@hpe.com>; devel@edk2.groups.io
Cc: Desimone, Ashley E <ashley.e.desimone@intel.com>
Subject: RE: FtdiUsbSerialDxe
Hi Jack,
To my knowledge, the code hasn't been touched at all since 2013 other than being moved from edk2 to edk2-platforms. The move from edk2 to edk2-platforms did happen in 2019, so perhaps something broke during that move but it seems unlikely. The only other explanation I can think of for it working with code from circa 2018 is that something in UsbBusDxe changed that broke FtdiUsbSerialDxe.
Thanks,
Nate
From: Little, Jack <jack.tay.little@hpe.com<mailto:jack.tay.little@hpe.com>>
Sent: Thursday, May 27, 2021 8:49 AM
To: Desimone, Nathaniel L <nathaniel.l.desimone@intel.com<mailto:nathaniel.l.desimone@intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Cc: Desimone, Ashley E <ashley.e.desimone@intel.com<mailto:ashley.e.desimone@intel.com>>
Subject: RE: FtdiUsbSerialDxe
Hi Nate,
The same FTDI device works with the source from around 05/23/2018, unsure of which chip is in there.
Thanks,
Jack
From: Desimone, Nathaniel L <nathaniel.l.desimone@intel.com<mailto:nathaniel.l.desimone@intel.com>>
Sent: Thursday, May 27, 2021 3:17 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Little, Jack <jack.tay.little@hpe.com<mailto:jack.tay.little@hpe.com>>
Cc: Desimone, Ashley E <ashley.e.desimone@intel.com<mailto:ashley.e.desimone@intel.com>>
Subject: RE: FtdiUsbSerialDxe
Hi Jack,
I believe that driver has only been tested with the FT232AM, which has not been manufactured for several years now. Ashley (cc'd) implemented it as an intern project in 2013: https://github.com/tianocore/edk2/commit/3f1484f
There probably needs to be some work done to get it running with newer FTDI chips like the FT232RL.
Thanks,
Nate
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> On Behalf Of Little, Jack
Sent: Wednesday, May 26, 2021 10:21 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: [edk2-devel] FtdiUsbSerialDxe
Hi,
Are there any known bugs with [edk2-stable202002] when using the FtdiUsbSerialDxe driver? I am seeing errors during initialization when TerminalDriverBindingStart() tries to reset the FTDI device and gets EFI_DEVICE_ERROR.
Thanks,
Jack
[-- Attachment #2: Type: text/html, Size: 6890 bytes --]
next prev parent reply other threads:[~2021-05-27 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 17:20 FtdiUsbSerialDxe Little, Jack
2021-05-27 8:17 ` FtdiUsbSerialDxe Nate DeSimone
2021-05-27 15:48 ` FtdiUsbSerialDxe Little, Jack
2021-05-27 16:05 ` FtdiUsbSerialDxe Nate DeSimone
2021-05-27 16:25 ` Little, Jack [this message]
2021-06-09 18:39 ` FtdiUsbSerialDxe Little, Jack
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-list 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=TU4PR8401MB0862B8C337F7DE89E86B4E6FAB239@TU4PR8401MB0862.NAMPRD84.PROD.OUTLOOK.COM \
--to=devel@edk2.groups.io \
/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