Thank you for the suggestion ; I already knew about this option, but have
intentionally chosen not to use it. Once the VIP/PID is changed, it will
no longer work with the Windows app that came with the cable to program the
radio (Yaesu FT-897d). When I choose to sell the radio, then I want to be
> On 10 Nov 2015, at 17:28, Burton Sampley wrote:
>
> I am having problems getting
> a a FTDI based USB to serial cable to provide CAT control to my Yaesu
> FT-897d amateur radio. The cable is made by RT-Systems with vendor ID
> 0x2100 and a product ID 0x9e56
Certainly not suitable to all situ
On 11/18/15 20:02, Burton Sampley wrote:
To All,
A quick update:
I really have no update. I have been attempting to get to the point where
I can test the newly built module, but I can not get my system to the point
where I can try the new module. I was able to compile it, but when I
attempted
To All,
A quick update:
I really have no update. I have been attempting to get to the point where
I can test the newly built module, but I can not get my system to the point
where I can try the new module. I was able to compile it, but when I
attempted to load the new module, I get the followin
On Wed, 2015-11-11 at 16:57 -0500, Burton Sampley wrote:
> Ian,
>
> Thank you for your prompt reply.
>
> Looking at the usbdevs file, I found 0x2100, but there is no entry
> for
> 0x9e56, which is my device. So, I'm assuming that changing uftdi.c
> to the
> correct name for the VID will only sol
Ian,
Thank you for your prompt reply.
Looking at the usbdevs file, I found 0x2100, but there is no entry for
0x9e56, which is my device. So, I'm assuming that changing uftdi.c to the
correct name for the VID will only solve part of my problem. I will
further assume that I need to find the corre
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 Nov 10, 2015 9:53 AM, "Hans Petter Selasky" wrote:
>
> On 11/10/15 17:50, Ian Lepore wrote:
>>
>> 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
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 digging to try to fix my own error.
Here's a diff of the original sour
On 11/10/15 18:14, Burton Sampley wrote:
Thank you. I do not have the kernel source on this system, so I will need
to setup the kernel source, then modify the table in uftdi.c with the
custom entries, then recompile the module and reload it. It may take some
time for me to complete these actions
Thank you. I do not have the kernel source on this system, so I will need
to setup the kernel source, then modify the table in uftdi.c with the
custom entries, then recompile the module and reload it. It may take some
time for me to complete these actions. Should I report back to this email
list
On 11/10/15 17:55, Burton Sampley wrote:
HPS,
Thank you for your prompt response. I reviewed the webpage link you have
provided. I assume that would be a template for an entry in
/etc/devd.conf, however what I do not understand is what is the FreeBSD
equivalent of "FTDI_SIO" that can be called
HPS,
Thank you for your prompt response. I reviewed the webpage link you have
provided. I assume that would be a template for an entry in
/etc/devd.conf, however what I do not understand is what is the FreeBSD
equivalent of "FTDI_SIO" that can be called in the "action" line?
The first step I wo
On 11/10/15 17:50, Ian Lepore wrote:
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?
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 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 plugged in, I
get the following in /var/log/messages:
Hi,
See examples here:
Greetings,
I am a long time FreeBSD user (started with FreeBSD 2.1.5R). I took a
break with FreeBSD for a while with a Linux desktop, but have recently
returned. I am now running a 10.2R desktop. I am having problems getting
a a FTDI based USB to serial cable to provide CAT control to my Yaesu
17 matches
Mail list logo
