From: John Ackermann (yeei.tgmojwbdi@mailit.tunk.net)
Date: Thu Dec 07 2000 - 19:24:49 EET
In message <wlmd@realcommerce.co.il> you wrote:
>On Thu, 07 Dec 2000, John Ackermann wrote:
>> In message <grh.ubjyur@roskapostia.tunk.net>
>> Tomi wrote:
>>
>> [ snip ]
>> >So to make use of the dmascc0 port, you should create a axports entry with
>> >any name and a unique callsign. Then set the hw address for the scc
>> >interface to that callsign: ifconfig dmascc0 hw ax25 <callsign>
>>
>> Aha!!! It's that last piece -- using ifconfig to assign the callsign --
>> that I hadn't thought of. Great idea, and I'll document it at my web
>> site (I don't think I've seen this issue discussed before).
>
>Then you have not read "scc_eng.doc"
>in your z8530drv-utils/doc directory.
>
>There are several examples there.
But I'm not using the z8530 driver; I'm using the dmascc driver. There is
no z8530drv-utils/doc directory on my system (I'm using Craig's .deb
packages, which apparently don't include z8530drv). The only doc
related to this driver seems to be the man page for the dmascc-config
program, and an almost identical README file, neither of which reference
this issue. The kernel sources make no mention either.
(Actually, though, I've used the scc driver in the past with a DRSI card,
and I already have a sample scc/DRSI config on my web site that does use
ifconfig to set the hardware addess -- I'd forgotten about that as I don't
use the DRSI card anymore. The point remains, though, that the information
on this is a bit obscure, and Tomi's explanation is enlightening for its
general applicability.)
73,
John
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to terhi.victor@logonet.com
This archive was generated by hypermail 2b30 : Thu Dec 07 2000 - 19:25:37 EET