diff for duplicates of <1467794679.3086.42.camel@synopsys.com> diff --git a/a/1.txt b/N1/1.txt index a628b3c..f2399c7 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,40 +1,40 @@ -Hi+AKA-Oleksij, +Hi?Oleksij, -On Wed, 2016-07-06 at 10:38 +-0200, fixed-term.Oleksij.Rempel wrote: -+AD4- -+AD4- On 06.07.2016 10:32, Alexey Brodkin wrote: -+AD4- +AD4- -+AD4- +AD4- Hi Oleksij, -+AD4- +AD4- -+AD4- +AD4- On Wed, 2016-07-06 at 10:24 +-0200, fixed-term.Oleksij.Rempel wrote: -+AD4- +AD4- +AD4- -+AD4- +AD4- +AD4- +AKA- -+AD4- +AD4- +AD4- Hm... this Endpoint should be Interrupt, not Bulk. If you search for -+AD4- +AD4- +AD4- lsusb of this kind of adapter all of them list EP3 and EP4 as Interrupt. -+AD4- +AD4- +AD4- -+AD4- +AD4- +AD4- what did went wrong here? Is it not working in USB High Speed mode? -+AD4- +AD4- Unfortunately as of now on that board EHCI doesn't work. -+AD4- +AD4- -+AD4- +AD4- That's not a problem of a particular USB device but something in either -+AD4- +AD4- ECHI host controller or its integration. I do hope we will fix it sometime soon -+AD4- +AD4- (this is a development board and USB controller is implemented in FPGA so -+AD4- +AD4- there's a chance to fix stuff later on). -+AD4- +AD4- -+AD4- +AD4- So given only OHCI works on the board I went forward and attempted to use it -+AD4- +AD4- with Wi-Fi USB dongle. -+AD4- -+AD4- I did some tests for 2 years on OHCI controller on x86. There was no -+AD4- noticable issues. It was even a bit faster then Intels EHCI. I don't -+AD4- think OHCI alone is the source of this problem. +On Wed, 2016-07-06@10:38 +0200, fixed-term.Oleksij.Rempel wrote: +> +> On 06.07.2016 10:32, Alexey Brodkin wrote: +> > +> > Hi Oleksij, +> > +> > On Wed, 2016-07-06@10:24 +0200, fixed-term.Oleksij.Rempel wrote: +> > > +> > > ? +> > > Hm... this Endpoint should be Interrupt, not Bulk. If you search for +> > > lsusb of this kind of adapter all of them list EP3 and EP4 as Interrupt. +> > > +> > > what did went wrong here? Is it not working in USB High Speed mode? +> > Unfortunately as of now on that board EHCI doesn't work. +> > +> > That's not a problem of a particular USB device but something in either +> > ECHI host controller or its integration. I do hope we will fix it sometime soon +> > (this is a development board and USB controller is implemented in FPGA so +> > there's a chance to fix stuff later on). +> > +> > So given only OHCI works on the board I went forward and attempted to use it +> > with Wi-Fi USB dongle. +> +> I did some tests for 2 years on OHCI controller on x86. There was no +> noticable issues. It was even a bit faster then Intels EHCI. I don't +> think OHCI alone is the source of this problem. Well I was also surprised how well that dongle works with that board in -OHCI mode. I saw quite consistent +AH4-4-5 Mbit/second rates when doing Speedtest +OHCI mode. I saw quite consistent ~4-5 Mbit/second rates when doing Speedtest from my smartphone. So IMHO it's completely usable. Especially on that kind of HW which has main CPU running at just 100MHz. -+AD4- On other side, so far i know, this adapter claims to provide usb full -+AD4- speed support, (Not only high speed) and may use different usb -+AD4- descriptor for this. May be this is the problem. +> On other side, so far i know, this adapter claims to provide usb full +> speed support, (Not only high speed) and may use different usb +> descriptor for this. May be this is the problem. So is there something we may do with all that? diff --git a/a/content_digest b/N1/content_digest index 0dd7376..30e780c 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,52 +6,52 @@ "ref\0577CC035.1000404@de.bosch.com\0" "ref\01467793848.3086.37.camel@synopsys.com\0" "ref\0577CC3A2.5070607@de.bosch.com\0" - "From\0Alexey Brodkin <Alexey.Brodkin@synopsys.com>\0" - "Subject\0[ath9k-devel] ath9k-htc on OHCI -> bogus usb xfer\0" + "From\0Alexey.Brodkin@synopsys.com (Alexey Brodkin)\0" + "Subject\0ath9k-htc on OHCI -> bogus usb xfer\0" "Date\0Wed, 6 Jul 2016 08:45:50 +0000\0" - "To\0ath9k-devel@lists.ath9k.org\0" + "To\0linux-snps-arc@lists.infradead.org\0" "\00:1\0" "b\0" - "Hi+AKA-Oleksij,\n" + "Hi?Oleksij,\n" "\n" - "On Wed, 2016-07-06 at 10:38 +-0200, fixed-term.Oleksij.Rempel wrote:\n" - "+AD4- \n" - "+AD4- On 06.07.2016 10:32, Alexey Brodkin wrote:\n" - "+AD4- +AD4- \n" - "+AD4- +AD4- Hi Oleksij,\n" - "+AD4- +AD4- \n" - "+AD4- +AD4- On Wed, 2016-07-06 at 10:24 +-0200, fixed-term.Oleksij.Rempel wrote:\n" - "+AD4- +AD4- +AD4- \n" - "+AD4- +AD4- +AD4- +AKA-\n" - "+AD4- +AD4- +AD4- Hm... this Endpoint should be Interrupt, not Bulk. If you search for\n" - "+AD4- +AD4- +AD4- lsusb of this kind of adapter all of them list EP3 and EP4 as Interrupt.\n" - "+AD4- +AD4- +AD4- \n" - "+AD4- +AD4- +AD4- what did went wrong here? Is it not working in USB High Speed mode?\n" - "+AD4- +AD4- Unfortunately as of now on that board EHCI doesn't work.\n" - "+AD4- +AD4- \n" - "+AD4- +AD4- That's not a problem of a particular USB device but something in either\n" - "+AD4- +AD4- ECHI host controller or its integration. I do hope we will fix it sometime soon\n" - "+AD4- +AD4- (this is a development board and USB controller is implemented in FPGA so\n" - "+AD4- +AD4- there's a chance to fix stuff later on).\n" - "+AD4- +AD4- \n" - "+AD4- +AD4- So given only OHCI works on the board I went forward and attempted to use it\n" - "+AD4- +AD4- with Wi-Fi USB dongle.\n" - "+AD4-\n" - "+AD4- I did some tests for 2 years on OHCI controller on x86. There was no\n" - "+AD4- noticable issues. It was even a bit faster then Intels EHCI. I don't\n" - "+AD4- think OHCI alone is the source of this problem.\n" + "On Wed, 2016-07-06@10:38 +0200, fixed-term.Oleksij.Rempel wrote:\n" + "> \n" + "> On 06.07.2016 10:32, Alexey Brodkin wrote:\n" + "> > \n" + "> > Hi Oleksij,\n" + "> > \n" + "> > On Wed, 2016-07-06@10:24 +0200, fixed-term.Oleksij.Rempel wrote:\n" + "> > > \n" + "> > > ?\n" + "> > > Hm... this Endpoint should be Interrupt, not Bulk. If you search for\n" + "> > > lsusb of this kind of adapter all of them list EP3 and EP4 as Interrupt.\n" + "> > > \n" + "> > > what did went wrong here? Is it not working in USB High Speed mode?\n" + "> > Unfortunately as of now on that board EHCI doesn't work.\n" + "> > \n" + "> > That's not a problem of a particular USB device but something in either\n" + "> > ECHI host controller or its integration. I do hope we will fix it sometime soon\n" + "> > (this is a development board and USB controller is implemented in FPGA so\n" + "> > there's a chance to fix stuff later on).\n" + "> > \n" + "> > So given only OHCI works on the board I went forward and attempted to use it\n" + "> > with Wi-Fi USB dongle.\n" + ">\n" + "> I did some tests for 2 years on OHCI controller on x86. There was no\n" + "> noticable issues. It was even a bit faster then Intels EHCI. I don't\n" + "> think OHCI alone is the source of this problem.\n" "\n" "Well I was also surprised how well that dongle works with that board in\n" - "OHCI mode. I saw quite consistent +AH4-4-5 Mbit/second rates when doing Speedtest\n" + "OHCI mode. I saw quite consistent ~4-5 Mbit/second rates when doing Speedtest\n" "from my smartphone. So IMHO it's completely usable. Especially on that kind of\n" "HW which has main CPU running at just 100MHz.\n" "\n" - "+AD4- On other side, so far i know, this adapter claims to provide usb full\n" - "+AD4- speed support, (Not only high speed) and may use different usb\n" - "+AD4- descriptor for this. May be this is the problem.\n" + "> On other side, so far i know, this adapter claims to provide usb full\n" + "> speed support, (Not only high speed) and may use different usb\n" + "> descriptor for this. May be this is the problem.\n" "\n" "So is there something we may do with all that?\n" "\n" -Alexey -24d2250c00ff78e78e21e8a529e96de1da0555f81103e31db575c28f830a23cd +86048a6e60224ab1ad5af3d1f49ee7bc3316b1f12926f71ec731f7391b29e4a2
diff --git a/a/1.txt b/N2/1.txt index a628b3c..457b39f 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,40 +1,40 @@ -Hi+AKA-Oleksij, +Hi Oleksij, -On Wed, 2016-07-06 at 10:38 +-0200, fixed-term.Oleksij.Rempel wrote: -+AD4- -+AD4- On 06.07.2016 10:32, Alexey Brodkin wrote: -+AD4- +AD4- -+AD4- +AD4- Hi Oleksij, -+AD4- +AD4- -+AD4- +AD4- On Wed, 2016-07-06 at 10:24 +-0200, fixed-term.Oleksij.Rempel wrote: -+AD4- +AD4- +AD4- -+AD4- +AD4- +AD4- +AKA- -+AD4- +AD4- +AD4- Hm... this Endpoint should be Interrupt, not Bulk. If you search for -+AD4- +AD4- +AD4- lsusb of this kind of adapter all of them list EP3 and EP4 as Interrupt. -+AD4- +AD4- +AD4- -+AD4- +AD4- +AD4- what did went wrong here? Is it not working in USB High Speed mode? -+AD4- +AD4- Unfortunately as of now on that board EHCI doesn't work. -+AD4- +AD4- -+AD4- +AD4- That's not a problem of a particular USB device but something in either -+AD4- +AD4- ECHI host controller or its integration. I do hope we will fix it sometime soon -+AD4- +AD4- (this is a development board and USB controller is implemented in FPGA so -+AD4- +AD4- there's a chance to fix stuff later on). -+AD4- +AD4- -+AD4- +AD4- So given only OHCI works on the board I went forward and attempted to use it -+AD4- +AD4- with Wi-Fi USB dongle. -+AD4- -+AD4- I did some tests for 2 years on OHCI controller on x86. There was no -+AD4- noticable issues. It was even a bit faster then Intels EHCI. I don't -+AD4- think OHCI alone is the source of this problem. +On Wed, 2016-07-06 at 10:38 +0200, fixed-term.Oleksij.Rempel wrote: +> +> On 06.07.2016 10:32, Alexey Brodkin wrote: +> > +> > Hi Oleksij, +> > +> > On Wed, 2016-07-06 at 10:24 +0200, fixed-term.Oleksij.Rempel wrote: +> > > +> > > +> > > Hm... this Endpoint should be Interrupt, not Bulk. If you search for +> > > lsusb of this kind of adapter all of them list EP3 and EP4 as Interrupt. +> > > +> > > what did went wrong here? Is it not working in USB High Speed mode? +> > Unfortunately as of now on that board EHCI doesn't work. +> > +> > That's not a problem of a particular USB device but something in either +> > ECHI host controller or its integration. I do hope we will fix it sometime soon +> > (this is a development board and USB controller is implemented in FPGA so +> > there's a chance to fix stuff later on). +> > +> > So given only OHCI works on the board I went forward and attempted to use it +> > with Wi-Fi USB dongle. +> +> I did some tests for 2 years on OHCI controller on x86. There was no +> noticable issues. It was even a bit faster then Intels EHCI. I don't +> think OHCI alone is the source of this problem. Well I was also surprised how well that dongle works with that board in -OHCI mode. I saw quite consistent +AH4-4-5 Mbit/second rates when doing Speedtest +OHCI mode. I saw quite consistent ~4-5 Mbit/second rates when doing Speedtest from my smartphone. So IMHO it's completely usable. Especially on that kind of HW which has main CPU running at just 100MHz. -+AD4- On other side, so far i know, this adapter claims to provide usb full -+AD4- speed support, (Not only high speed) and may use different usb -+AD4- descriptor for this. May be this is the problem. +> On other side, so far i know, this adapter claims to provide usb full +> speed support, (Not only high speed) and may use different usb +> descriptor for this. May be this is the problem. So is there something we may do with all that? diff --git a/a/content_digest b/N2/content_digest index 0dd7376..c27e49a 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -7,51 +7,57 @@ "ref\01467793848.3086.37.camel@synopsys.com\0" "ref\0577CC3A2.5070607@de.bosch.com\0" "From\0Alexey Brodkin <Alexey.Brodkin@synopsys.com>\0" - "Subject\0[ath9k-devel] ath9k-htc on OHCI -> bogus usb xfer\0" + "Subject\0Re: ath9k-htc on OHCI -> bogus usb xfer\0" "Date\0Wed, 6 Jul 2016 08:45:50 +0000\0" - "To\0ath9k-devel@lists.ath9k.org\0" + "To\0fixed-term.Oleksij.Rempel@de.bosch.com <fixed-term.Oleksij.Rempel@de.bosch.com>\0" + "Cc\0linux-wireless@vger.kernel.org <linux-wireless@vger.kernel.org>" + anders.darander@gmail.com <anders.darander@gmail.com> + ath9k-devel@lists.ath9k.org <ath9k-devel@lists.ath9k.org> + linux@rempel-privat.de <linux@rempel-privat.de> + linux-snps-arc@lists.infradead.org <linux-snps-arc@lists.infradead.org> + " linux-usb@vger.kernel.org <linux-usb@vger.kernel.org>\0" "\00:1\0" "b\0" - "Hi+AKA-Oleksij,\n" + "Hi\302\240Oleksij,\n" "\n" - "On Wed, 2016-07-06 at 10:38 +-0200, fixed-term.Oleksij.Rempel wrote:\n" - "+AD4- \n" - "+AD4- On 06.07.2016 10:32, Alexey Brodkin wrote:\n" - "+AD4- +AD4- \n" - "+AD4- +AD4- Hi Oleksij,\n" - "+AD4- +AD4- \n" - "+AD4- +AD4- On Wed, 2016-07-06 at 10:24 +-0200, fixed-term.Oleksij.Rempel wrote:\n" - "+AD4- +AD4- +AD4- \n" - "+AD4- +AD4- +AD4- +AKA-\n" - "+AD4- +AD4- +AD4- Hm... this Endpoint should be Interrupt, not Bulk. If you search for\n" - "+AD4- +AD4- +AD4- lsusb of this kind of adapter all of them list EP3 and EP4 as Interrupt.\n" - "+AD4- +AD4- +AD4- \n" - "+AD4- +AD4- +AD4- what did went wrong here? Is it not working in USB High Speed mode?\n" - "+AD4- +AD4- Unfortunately as of now on that board EHCI doesn't work.\n" - "+AD4- +AD4- \n" - "+AD4- +AD4- That's not a problem of a particular USB device but something in either\n" - "+AD4- +AD4- ECHI host controller or its integration. I do hope we will fix it sometime soon\n" - "+AD4- +AD4- (this is a development board and USB controller is implemented in FPGA so\n" - "+AD4- +AD4- there's a chance to fix stuff later on).\n" - "+AD4- +AD4- \n" - "+AD4- +AD4- So given only OHCI works on the board I went forward and attempted to use it\n" - "+AD4- +AD4- with Wi-Fi USB dongle.\n" - "+AD4-\n" - "+AD4- I did some tests for 2 years on OHCI controller on x86. There was no\n" - "+AD4- noticable issues. It was even a bit faster then Intels EHCI. I don't\n" - "+AD4- think OHCI alone is the source of this problem.\n" + "On Wed, 2016-07-06 at 10:38 +0200, fixed-term.Oleksij.Rempel wrote:\n" + "> \n" + "> On 06.07.2016 10:32, Alexey Brodkin wrote:\n" + "> > \n" + "> > Hi Oleksij,\n" + "> > \n" + "> > On Wed, 2016-07-06 at 10:24 +0200, fixed-term.Oleksij.Rempel wrote:\n" + "> > > \n" + "> > > \302\240\n" + "> > > Hm... this Endpoint should be Interrupt, not Bulk. If you search for\n" + "> > > lsusb of this kind of adapter all of them list EP3 and EP4 as Interrupt.\n" + "> > > \n" + "> > > what did went wrong here? Is it not working in USB High Speed mode?\n" + "> > Unfortunately as of now on that board EHCI doesn't work.\n" + "> > \n" + "> > That's not a problem of a particular USB device but something in either\n" + "> > ECHI host controller or its integration. I do hope we will fix it sometime soon\n" + "> > (this is a development board and USB controller is implemented in FPGA so\n" + "> > there's a chance to fix stuff later on).\n" + "> > \n" + "> > So given only OHCI works on the board I went forward and attempted to use it\n" + "> > with Wi-Fi USB dongle.\n" + ">\n" + "> I did some tests for 2 years on OHCI controller on x86. There was no\n" + "> noticable issues. It was even a bit faster then Intels EHCI. I don't\n" + "> think OHCI alone is the source of this problem.\n" "\n" "Well I was also surprised how well that dongle works with that board in\n" - "OHCI mode. I saw quite consistent +AH4-4-5 Mbit/second rates when doing Speedtest\n" + "OHCI mode. I saw quite consistent ~4-5 Mbit/second rates when doing Speedtest\n" "from my smartphone. So IMHO it's completely usable. Especially on that kind of\n" "HW which has main CPU running at just 100MHz.\n" "\n" - "+AD4- On other side, so far i know, this adapter claims to provide usb full\n" - "+AD4- speed support, (Not only high speed) and may use different usb\n" - "+AD4- descriptor for this. May be this is the problem.\n" + "> On other side, so far i know, this adapter claims to provide usb full\n" + "> speed support, (Not only high speed) and may use different usb\n" + "> descriptor for this. May be this is the problem.\n" "\n" "So is there something we may do with all that?\n" "\n" -Alexey -24d2250c00ff78e78e21e8a529e96de1da0555f81103e31db575c28f830a23cd +61685262319ec7765e12717fa5c20bab6768b681d9453e202e43a8e3287b5fca
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.