> On 3 Oct 2019, at 17:41, Hans Petter Selasky wrote:
>
> On 2019-10-03 09:37, O'Connor, Daniel wrote:
>>> On 3 Oct 2019, at 17:01, Hans Petter Selasky wrote:
>>> On 2019-10-03 08:56, O'Connor, Daniel wrote:
>>>> Most of USB-serial devices have "ve
> On 3 Oct 2019, at 17:01, Hans Petter Selasky wrote:
> On 2019-10-03 08:56, O'Connor, Daniel wrote:
>> Most of USB-serial devices have "very stable" serial number:)
>> more than 50% have S/N "0123456789".
>
> It is also allowed to have no se
asic
script modifications.
Perhaps I should have made /dev/usbserialbysn and put symlinks in that.
> Thanks.
>
>
> чт, 3 жовт. 2019 о 05:56 O'Connor, Daniel пише:
> Hi,
> I have several USB serial ports on a machine and I don't want to rely on
> attach order to get variou
Hi,
I have several USB serial ports on a machine and I don't want to rely on attach
order to get various programs to talk to the correct serial port.
I wrote the following devd script and shell script to create symlinks from
cu.${sernum}/tty.${sernum} to the real device nodes.
I post it here
> On 8 Sep 2019, at 23:12, Konstantin Belousov wrote:
>> I suppose it would be good to change it to the same structure as the feed
>> forward clock stuff, that way it is much easier to change the number of
>> hands at compile time..
>>
>
> The reason to not increase it by default is the
> On 20 Aug 2019, at 11:37, O'Connor, Daniel wrote:
>
>
>
>> On 19 Aug 2019, at 17:09, O'Connor, Daniel wrote:
>> I am going to try this diff but buildkernel is going to take a while...
>
> Was a lot faster cross building, so I installed it this morning:
>
> On 19 Aug 2019, at 17:09, O'Connor, Daniel wrote:
> I am going to try this diff but buildkernel is going to take a while...
Was a lot faster cross building, so I installed it this morning:
[gps 1:56] ~ >uname -a
FreeBSD gps 13.0-CURRENT FreeBSD 13.0-CURRENT #1
41a4c010326-c2621
> On 6 Aug 2019, at 00:12, Ian Lepore wrote:
> On Mon, 2019-08-05 at 15:28 +0930, O'Connor, Daniel wrote:
>>> Most people are not worried about their kernel clock being 200
>>> microseconds off from UTC, even if they're using the PPS signal from a
>>> GPS
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 port
> on a USB 2.0 hub that's connected to a USB 2.0 host port on the
> Wandboard.
>
> PPS(3) is an FTDI
> On 3 May 2019, at 02:31, Hans Petter Selasky wrote:
>
> On 2019-05-02 13:38, O'Connor, Daniel wrote:
>>> On 2 May 2019, at 20:33, Hans Petter Selasky wrote:
>>>
>>> On 2019-05-02 12:44, O'Connor, Daniel wrote:
>>>>> On 2 May 2019, at 20:0
> On 2 May 2019, at 20:33, Hans Petter Selasky wrote:
>
> On 2019-05-02 12:44, O'Connor, Daniel wrote:
>>> On 2 May 2019, at 20:02, Hans Petter Selasky wrote:
>>>
>>> On 2019-05-02 11:18, O'Connor, Daniel wrote:
>>>> OK, thanks.
>&
> On 2 May 2019, at 20:02, Hans Petter Selasky wrote:
>
> On 2019-05-02 11:18, O'Connor, Daniel wrote:
>> OK, thanks.
>> To be honest I would much prefer to work out why this particular hardware &
>> software seem to drop the ball for such a long time - 50msec
> On 2 May 2019, at 18:06, Hans Petter Selasky wrote:
> On 2019-05-02 10:22, O'Connor, Daniel wrote:
>>> On 2 May 2019, at 06:15, Hans Petter Selasky wrote:
>>> On 2019-05-01 10:34, O'Connor, Daniel wrote:
>>>> I don't have a solid hypothesis for t
> On 2 May 2019, at 06:15, Hans Petter Selasky wrote:
> On 2019-05-01 10:34, O'Connor, Daniel wrote:
>> I don't have a solid hypothesis for the failures as yes but one thing I'd
>> like to make sure is that the USB stack is keeping the USB hardware busy
>> with pendin
Hi,
I have a device driver for a USB device (a custom Cypress FX2 based board) that
is relatively simple - it uses the USB FIFO code to create 3 FIFOs (one
bidirectional slow serial interface, one device->PC fast parallel interface
from a hardware FIFO) plus a bunch of ioctls for getting the
> On 23 Jul 2016, at 02:05, O. Hartmann wrote:
>
> I tried to load any available USB serial port/adaptor driver available to
> make this
> sensor attach as a ttyU? as it does in Linux (/dev/ttyUSB), but no luck so
> far. I'm not
> familiar with serial consoles or
16 matches
Mail list logo