On Tue, 2020-09-01 at 16:23 +0200, Willem Jan Withagen wrote:
> On 1-9-2020 16:10, Hans Petter Selasky wrote:
> > On 2020-09-01 15:54, Willem Jan Withagen wrote:
> > > Could it be because the dongle itself crashes?
> >
> > Yes, if they reboot or there are disturbances on the USB cables, then
> >
On Sun, 2020-05-31 at 22:11 +0200, Tomasz CEDRO wrote:
> On Sun, May 31, 2020 at 7:54 PM Hans Petter Selasky wrote:
> >
> > [...]
>
> I use MINICOM as the Terminal emulator. Type Ctrl+A then Z for command
> menu. Note that you will have to create a configuration for a given
> port in the first pl
On Mon, 2020-03-02 at 16:19 -0500, Farhan Khan wrote:
> Hi all,
>
> I am trying to understand how FreeBSD's usb transfers work compared
> to OpenBSD by using the rum(4) driver. I am a little confused how the
> FreeBSD side works.
>
> On the OpenBSD side, it seems that after allocating the pipes,
On Mon, 2019-08-19 at 17:09 +0930, O'Connor, Daniel wrote:
> > On 12 Aug 2019, at 09:09, O'Connor, Daniel
> > wrote:
> > > always get lost on single-core processors which are in cpu_idle()
> > > at
> > > the time the hardclock interrupt happens. (But that's fixable by
> > > just
> > > increasing
On Mon, 2019-08-05 at 15:28 +0930, O'Connor, Daniel wrote:
> Hi Ian,
>
> Firstly, this is a very cool test - thank you for running it :)
>
> > On 3 Aug 2019, at 06:46, Ian Lepore wrote:
> > PPS(2) is an FTDI 232R, a USB 1.1 serial adapter, connected to a por
Since we added support for accepting a PPS signal on a USB-serial
adapter a couple years ago, I've seen people express reluctance to use
it several times. Usually they cite concerns about latency and
jitter. I decided it was time to do some rigorous testing, and post
the results.
Complete deta
On Mon, 2019-02-18 at 15:03 -0600, Apollo D. Sharpe, Sr. via freebsd-
usb wrote:
> On 2/18/19 3:26 AM, Hans Petter Selasky wrote:
> > Each devicename has a uniq prefix followed by a uniq unit number.
>
> So, we just end up dumping ALL device nodes in /dev...
>
>
> > Character device nodes are au
On Sun, 2018-11-04 at 19:05 -0500, Mike Andrews wrote:
> On Fri, 2 Nov 2018, CeDeROM wrote:
>
> >
> > Try to add VID/PID of your device into a usbmodem driver. Use
> > configurations to see which one works with your device. Rebuild the
> > module/kernel, reboot, try it out untill success.
> >
>
On Mon, 2017-10-02 at 00:05 +0200, Tomasz CEDRO wrote:
> On Sun, Oct 1, 2017 at 10:59 PM, Ian Lepore wrote:
> >
> > On Sun, 2017-10-01 at 22:20 +0200, Tomasz CEDRO wrote:
> > >
> > > On Sun, Oct 1, 2017 at 9:38 PM, Ian Lepore
> > > wrote:
> > &
On Sun, 2017-10-01 at 22:20 +0200, Tomasz CEDRO wrote:
> On Sun, Oct 1, 2017 at 9:38 PM, Ian Lepore wrote:
> >
> > On Sun, 2017-10-01 at 20:59 +0200, Tomasz CEDRO wrote:
> > >
> > > On Sun, Oct 1, 2017 at 8:23 PM, Ian Lepore
> > > wrote:
> > &
On Sun, 2017-10-01 at 20:59 +0200, Tomasz CEDRO wrote:
> On Sun, Oct 1, 2017 at 8:23 PM, Ian Lepore wrote:
> >
> > On Sun, 2017-10-01 at 20:17 +0200, Tomasz CEDRO wrote:
> > >
> > > [...old stuff...]
> I have verified on uath device (more on that below) and i
On Sun, 2017-10-01 at 20:17 +0200, Tomasz CEDRO wrote:
> On Sun, Oct 1, 2017 at 7:21 PM, Hans Petter Selasky
> wrote:
> >
> > On 10/01/17 19:09, Tomasz CEDRO wrote:
> > >
> > >
> > > On Sun, Oct 1, 2017 at 6:40 PM, Ian Lepore
> > > wrote:
On Sun, 2017-10-01 at 18:33 +0200, Tomasz CEDRO wrote:
> On Wed, Sep 27, 2017 at 8:32 AM, Hans Petter Selasky > wrote:
> >
> > On 09/27/17 00:37, Ian Lepore wrote:
> > >
> > >
> > > On Wed, 2017-09-27 at 00:30 +0200, Hans Petter Selasky wrote
On Wed, 2017-09-27 at 00:30 +0200, Hans Petter Selasky wrote:
> On 09/27/17 00:11, Tomasz CEDRO wrote:
> >
> > https://github.com/freebsd/freebsd/pull/115
> >
> > :-)
> >
> The devd.conf rule should match more than just vendor and product:
>
>
> +# Load GOBI 2000/3000 U3G QDL modem firmware on
On Sun, 2016-07-24 at 12:52 -0600, Warner Losh wrote:
> On Sun, Jul 24, 2016 at 12:42 PM, Kevin Oberman
> wrote:
> > There are several different USB serial drivers. Off-hand I see
> > ubser, ubsa,
> > uchcom, ucom, ucycom, uftdi, ubgensa, umcs, umct, umoscom, uplcom,
> > usb_serial, uslcom, and uv
On Sun, 2016-07-24 at 10:51 +0200, O. Hartmann wrote:
> Am Sun, 24 Jul 2016 08:38:59 +0200
> Gary Jennejohn schrieb:
>
> > On Sun, 24 Jul 2016 08:03:30 +0200
> > "O. Hartmann" wrote:
> >
> > > Am Sat, 23 Jul 2016 14:49:11 -0600
> > > Ian
On Sat, 2016-07-23 at 22:04 +0200, O. Hartmann wrote:
> Am Fri, 22 Jul 2016 10:52:54 -0600
> Ian Lepore schrieb:
>
> > On Fri, 2016-07-22 at 18:35 +0200, O. Hartmann wrote:
> > > For temperature monitoring, we have a bunch of Digi Watchport/T
> > > sensors:
On Fri, 2016-07-22 at 18:35 +0200, O. Hartmann wrote:
> For temperature monitoring, we have a bunch of Digi Watchport/T
> sensors:
>
> http://ftp1.digi.com/support/documentation/9406_H.pdf
>
>
[...]
I think the attached patch will make it show up as a ttyU*/cuaU* device
for you. (You shou
t; bNumConfigurations = 0x0001
>
> $
>
> does "CT-62B" look reasonable?
>
Yep, you'll have to add a new entry to usbdevs for the the 0x9e56
device. CT62B seems like a good name (can't put the dash in the name
for C syntax reasons).
-- Ian
>
> Rega
On Wed, 2015-11-11 at 16:28 -0500, Burton Sampley wrote:
> I added a line to the table, but it seems to have failed since I used
> the
> VID# instead of the VID# name. Where are the VID names mapped to the
> VID#'s? Apparently, I know enough about coding to be dangerous.
> I'll do
> some more d
On Tue, 2015-11-10 at 17:40 +0100, Hans Petter Selasky wrote:
> On 11/10/15 17:28, Burton Sampley wrote:
> > SYSFS{idVendor}=="2100", SYSFS{idProduct}=="9e56",
> > RUN+="/sbin/modprobe -q
> > ftdi_sio vendor=0x2100 product=0x9e56"
> >
> > How do I accomplish the same in FreeBSD? When the cable is
On Tue, 2015-02-24 at 21:47 +, bugzilla-nore...@freebsd.org wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198015
>
> Bug ID: 198015
>Summary: devd(8) overwrites "bus" on ugen event
>Product: Base System
>Version: 10.1-RELEASE
>
On Wed, 2015-01-14 at 06:13 +0100, Hans Petter Selasky wrote:
> On 01/13/15 21:25, Ian Lepore wrote:
> > On Tue, 2015-01-13 at 17:52 +0100, Hans Petter Selasky wrote:
> >> On 01/13/15 17:29, Ian Lepore wrote:
> >>> On Tue, 2015-01-13 at 16:57 +0100, Hans Petter Sel
On Tue, 2015-01-13 at 17:52 +0100, Hans Petter Selasky wrote:
> On 01/13/15 17:29, Ian Lepore wrote:
> > On Tue, 2015-01-13 at 16:57 +0100, Hans Petter Selasky wrote:
> >> On 01/13/15 16:40, Ian Lepore wrote:
> >>> On Tue, 2015-01-13 at 16:27 +0100, Hans Petter Selask
On Tue, 2015-01-13 at 16:57 +0100, Hans Petter Selasky wrote:
> On 01/13/15 16:40, Ian Lepore wrote:
> > On Tue, 2015-01-13 at 16:27 +0100, Hans Petter Selasky wrote:
> >> On 01/13/15 15:49, Ian Lepore wrote:
> >>> On Tue, 2015-01-13 at 00:14 -0700, kott wrote:
> &
On Tue, 2015-01-13 at 16:27 +0100, Hans Petter Selasky wrote:
> On 01/13/15 15:49, Ian Lepore wrote:
> > On Tue, 2015-01-13 at 00:14 -0700, kott wrote:
> >> Yes with cache disabled, this problem is not seen. Seems to be with a issue
> >> with l2 cache.
> >> T
On Tue, 2015-01-13 at 00:14 -0700, kott wrote:
> Yes with cache disabled, this problem is not seen. Seems to be with a issue
> with l2 cache.
> Thanks kott
Except that there are no known problems with l2 cache on armv7 right
now. There are known problems with the USB driver using the busdma
routi
On Mon, 2014-12-22 at 10:48 +0100, Hans Petter Selasky wrote:
> On 12/22/14 10:31, Kohji Okuno wrote:
> > In an optimisation, we should reduce the number of LINK_TRB, too.
> > I heard from a LSI engineer that,
> > Generally xhci controler has the cache of TRB array. But, LINK_TRB
> > may make the
The following reply was made to PR usb/188683; it has been noted by GNATS.
From: Ian Lepore
To: John Wehle
Cc: freebsd-gnats-sub...@freebsd.org
Subject: Re: usb/188683: dwc_otg FDT support for specifying usb controller
mode
Date: Wed, 16 Apr 2014 07:09:26 -0600
On Wed, 2014-04-16 at 07:17
The attached patch, which I hope to commit sometime soon, adds support
for bitbang, MPSSE, CPU_FIFO, and other modes supported by the FTDI
serial adapter chips, using ioctl() calls. This allows full control of
all the FTDI features that embedded folks like, using any language that
supports fd-base
I have added support to the uftdi driver for the higher baud rates
supported by the latest H-series chips. I hope to commit the changes
soon; the patch is attached for review.
In the process I discovered we've been setting the rate wrong on the
older chips (we put the high bit of the fractional r
On Tue, 2013-09-17 at 23:08 +0400, Lev Serebryakov wrote:
> Hello, Harald.
> You wrote 17 сентября 2013 г., 21:43:17:
>
> HS> Is that worth a try?
> HS>
> http://www.asix.com.tw/FrootAttach/driver/MCS7840_7820_FreeBSD_driver_v1.1.zip
> Nope. I've started from this driver, and it even doesn't su
On Tue, 2013-09-17 at 19:32 +0200, Harald Schmalzbauer wrote:
> Bezüglich Ian Lepore's Nachricht vom 17.09.2013 18:16 (localtime):
> > On Tue, 2013-09-17 at 17:38 +0200, Harald Schmalzbauer wrote:
> >> ...
> >>> Try this patch and see what happens:
> >>>
> >>> ==
On Tue, 2013-09-17 at 17:38 +0200, Harald Schmalzbauer wrote:
> Bezüglich Hans Petter Selasky's Nachricht vom 17.09.2013 11:24
> (localtime):
> > On 09/17/13 11:06, Harald Schmalzbauer wrote:
> >> ...
> >> Shall we switch to non-list-comm?
> >
> > Hi,
> >
> > That's OK.
> >
> >> Hmm, in my case, th
34 matches
Mail list logo
