> On Dec 22, 2015, at 11:40 PM, Theo de Raadt
wrote:
>
>> I originally set all the ports to PUC_COM_POW2(3) and I did communicate
>> with one of the ports to a different machine @ 115200.
>> In the next few days, I will test all the ports @ 115200 and 9600.
>
> Ok great.
Hi Jordon,
Please send future diffs to tech@; misc@ is for trolls ;)
> I'm still not sure why the first four ports give the probe message
> and the second four don't. If this is adequate testing, feel free
> to add this. If more testing is preferred, let me know what to do.
The card is
> On Dec 26, 2015, at 4:15 PM, Mark Kettenis wrote:
>
> Hi Jordon,
>
> Please send future diffs to tech@; misc@ is for trolls ;)
Will do.
>> I'm still not sure why the first four ports give the probe message
>> and the second four don't. If this is adequate testing,
> On Dec 22, 2015, at 6:20 PM, Stuart Henderson wrote:
>
> On 2015-12-22, Jordon >
wrote:
>> I have actually made some progress on this serial port card! I looked at
how
>> FreeBSD has it configured, tried to map the values
On 2015-12-22, Jordon wrote:
> I have actually made some progress on this serial port card! I looked at how
> FreeBSD has it configured, tried to map the values to the OpenBSD struct, and
> actually got something working!
>
>
>
> I added the following to pcidevs:
>
> vendor
> On Dec 22, 2015, at 8:03 PM, Theo de Raadt wrote:
>
> Can you send me a pcidump -v?
>
> Look for
>
>0x002c: Subsystem Vendor ID: Product ID:
>
> in those listings, and try adding those to your table in the
> right place, rather than 0x with a
I have actually made some progress on this serial port card! I looked at how
FreeBSD has it configured, tried to map the values to the OpenBSD struct, and
actually got something working!
I added the following to pcidevs:
vendor PERLE 0x155f Perle
vendor COMTROL 0x11fe
7 matches
Mail list logo