<SNIP>

> * In /etc/conf.modules I put
> 
>         alias tty-ldisc-11 irtty
> 
>         alias char-major-161 ircomm_tty
> 
>   I saw that in many items of documentation it says
> 
>         alias char-major-161 ircomm-tty
> 
>   with a dash instead of an underscore, but doing that justs results in
> a module not being found. I am curious about this, though, since the
> dash comes up again in some mails I found on the Linux-IrDA mailing
> list.

Something about two versions of the IRCOMM-driver. Not sure why. I have this in
my conf.modules:
  
# IrDA
alias tty-ldisc-11 irtty
alias char-major-161 ircomm-tty

<SNIP>

<SNIP> 
>         # irattach /dev/ircomm0
> 

Drop using irmanager. Use the following:

irattach /dev/ttyS1 -s 1

That is: you need to ATTAC the IR to a TTY (namely the one, where the IR-port
presents itself. On my laptop, the IR-port is com2, hence the above works for
me. The -s 1 means "discovery on". Discovering the semantics of -s 0 are left as
an exercise to you :)

 
<SNIP> 
>         # cu -l /dev/ttyS2
> 

HERE you use /dev/ircomm0 instead. Then it will all be dandy :)

In short: Your IR-port lives as a "serial port" (sort of - has an UART and
stuff and presents itself as such). Using irattach, you tie that port to the
IrDA-code, and by accessing /dev/ircomm0, you will be able to communicate
through the IrDA-stack to the ttyS and into the "air" :)

Sent in private since 1) I am not an "official" IrDA-person and 2) the above is
slightly inaccurate however usefull for "the craftsman" who wants to get things
working.

Have fun - the SH888 works fine with my ThinkPad :)

 
-- 
Mange hilsner / Sincerely

-------------------------------------------
  Thomas Heide Clausen
  Civilingeni�r i Datateknik (cand.polyt)
  M.Sc in Computer Engineering

  E-Mail: [EMAIL PROTECTED]
  WWW:    http://www.cs.auc.dk/~voop
-------------------------------------------

_______________________________________________
Linux-IrDA mailing list  -  [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda

Reply via email to