K.S.Sathish wrote :
> After receiving Jean's response, i have gone to make use of the
> irport driver which comes along with the 2.4.18 kernel , running on
> the SH4 based Aspen/Tahoe board.
It's a shame that the SH guys can't fix their bugs.
By the way, 2.4.18 is old, you may want to backport the IrDA
stack from 2.4.22 into 2.4.18.
> > Nov 2 21:28:31 dolphin kernel: NETDEV WATCHDOG: irda0: transmit timed out
> > Nov 2 21:28:31 dolphin kernel: irda0: transmit timed out
> > Nov 2 21:28:38 dolphin kernel: NETDEV WATCHDOG: irda0: transmit timed out
> > Nov 2 21:28:38 dolphin kernel: irda0: transmit timed out
> > Nov 2 21:29:05 dolphin kernel: NETDEV WATCHDOG: irda0: transmit timed out
> > Nov 2 21:29:05 dolphin kernel: irda0: transmit timed out
Take the irport driver available in 2.6.0, this should fix
this problem. It should be a straightforward backport to 2.4.X.
The reason I haven't updated irport in 2.4.X is because
smc-ircc depend on it and I can't test this hardware. In 2.6.X we have
smsc-ircc2, so I can take the risk to break smc-ircc ;-)
> I have another question in general, is there any way to test the
> IrDA interface without using any external IR devices
Not that I know. Use a Palm or another Linux box.
Have fun...
Jean

Hello all,
After receiving Jean's response, i have gone to make use of the irport driver
which comes along with the 2.4.18 kernel , running on the SH4 based Aspen/Tahoe
board.
I have the stack as part of the kernel rather than as modules and i load the
irport driver as a module. I am bringing up the irda interface by saying
"ifconfig irda0 up".
I do a "echo 1 > /proc/sys/net/irda/discovery" to start the discovery.
"echo 115200 > /proc/sys/net/irda/max_baud_rate".
In order to test the IrDA interface on the Aspen/Tahoe board i have built the
pilot-link utilities. At first i tried to place the Palm IIIxe device close to
the IR port and ran a "./dlpsh -p /dev/ircomm0" command on the shell prompt
after exporting PILOTRATE=115200 on the Aspen board.
I get the same messages as earlier posted on the web which says
"
>
> Nov 2 21:28:31 dolphin kernel: NETDEV WATCHDOG: irda0: transmit timed out
> Nov 2 21:28:31 dolphin kernel: irda0: transmit timed out
> Nov 2 21:28:38 dolphin kernel: NETDEV WATCHDOG: irda0: transmit timed out
> Nov 2 21:28:38 dolphin kernel: irda0: transmit timed out
> Nov 2 21:29:05 dolphin kernel: NETDEV WATCHDOG: irda0: transmit timed out
> Nov 2 21:29:05 dolphin kernel: irda0: transmit timed out
Yep, I have the same problem when I try irport. It seems that
somehow we drop/miss a Tx-done interrupt (UART_IIR_THRI). I tried to
investigate that but came empty handed.
I looked a the new smsc-ircc2 driver, and I suspect that what
you see is another manifestation of the exact same problem.
"
Does a solution exist for the above message, if so please let me know because i
was not able to find it.
I have another question in general, is there any way to test the IrDA interface
without using any external
IR devices such as loopback.I would like to use the loopback facility, but what
is the device name which represent
irport driver.
Can anyone please let me know where am i going wrong.
Please let me know if any other information is required.
Thanks for the help in advance.
-Sathish
Message: 9
Date: Tue, 22 Jul 2003 11:52:01 -0700
To: irda-users@...
From: Jean Tourrilhes <jt@...>
Subject: [irda-users] Re: Facing problem with irattach utility
Reply-To: irda-users@...
K.S.Sathish wrote :
>
> Jun 7 22:12:29 130 user.err irattach: ioctl(TIOCGETD): Invalid argument
It looks like the TTY layer is broken on SH4. This is not even
involving the IrDA stack.
The corresponding code is :
------------------------------
if (ioctl(ttyfd, TIOCGETD, &initdisc) < 0) {
syslog(LOG_ERR, "ioctl(TIOCGETD): %m");
clean_exit(-1);
}
------------------------------
This has always worked for me in various platforms, and this
is TTY generic, so you may want to bring that on the SH mailing lists.
Good luck...
Jean

Andrey Borzenkov wrote :
>
> This compiles and loads but I am not sure how to test it, I do not actually
> have any ircomm device currently.
>
> -andrey
Yes, I forgot to do that. This looks like the right patch,
would you mind sending it to me ?
Thanks !
Jean

irtty is dabbed as broken in Makefile.
Question - is it fundamentally broken, sometimes broken or under special
conditions broken? :)
I need to decide if I replace default ldisc-11 by irtty-sir in 2.6 (risking
that some dongles stop working for some people) or leave it as irtty and tell
guys who build kernel to use CONFIG_IRTTY_OLD
TIA
-andrey

On Fri, Jul 25, 2003 at 11:25:54PM +0000, angel@... wrote:
> Hi Jean:
> I'm not a developer, and english is not my native language... :-)
English isn't mine either.
> I think this log can be usefull to this patch.
> This a log of minicom trying to use /dev/ircomm0 in a clone laptop with
> via vt8231 southbridge
> I think this patch have a error because i can't connect to ircomm device,
> perhaps i miss something in configuration, but it seems a error int any point
> of initilizing: ircomm_tty_write() : not initialised
This is not the problem, the problem seems to happen much before.
> My kernel version is 2.6.0-test1 which a patch you send in 2003-07-09
> I only try without passing any dongle_id to module, i think it must be set to
> default value 9. irdadump shows drivers found my handheld device and linux
> node
This log is useless without the corresponding irdadump. And
also, you did cut the driver initialisation log, which I would be
interested in.
By the way, the lastest patch is on my web page, but it
probably is not different.
Regards,
Jean
----------------------------
Real problems to look into :
> irlmp_state_setup() WATCHDOG_TIMEOUT!
> IrLAP, no activity on link!
> irlap_driver_rcv(), wrong connection address!
The third one is *really* scary.

Dear Jean,
On Vin 25 Iul 2003 02:19, Jean Tourrilhes wrote:
> Claudiu Costin wrote :
> > There's a new batch of changes completed on the site.
> > Here is the news:
> >
> > "Site update and new development irda-utils 0.9.16 package
>
> I really appreciate the work you are putting in there.
Thank you very much for your kind words.
>
> > P.S. For the moment it's seems that the SourceForge
> > webserver doesn't work so please be patient if
>
> The mailing list archive and CVS seems to be even more flaky.
Because I work with the SF.NET CVS almost daily, I can say it work
very good. May be you may have complaints for web cvs interface.
I not checked the mailing list archive for some time :)
kind regards and have a nice weekend,
--
Claudiu Costin, claudiuc@...
Linux-KDE Romania http://www.ro.kde.org

Claudiu Costin wrote :
> There's a new batch of changes completed on the site.
> Here is the news:
>
> "Site update and new development irda-utils 0.9.16 package
I really appreciate the work you are putting in there.
> P.S. For the moment it's seems that the SourceForge
> webserver doesn't work so please be patient if
The mailing list archive and CVS seems to be even more flaky.
Have fun...
Jean

Dear friends,
There's a new batch of changes completed on the site.
Here is the news:
"Site update and new development irda-utils 0.9.16 package
There are lot of new things on the site. The Status page have now sections
more easy to follow. On Documentation, even if first page is yet not finished,
the Starting IrDA, Communicating and Advanced are now fully revamped.
FTP area was synchronized with latest patches from Jean's IrDA page and new
development irda-utils packages are available.
Stick on irda-utils 0.9.16-pre6."
Read the news with all the links at:
http://irda.sourceforge.net/home.html
P.S. For the moment it's seems that the SourceForge
webserver doesn't work so please be patient if
you read this mail right in the new few hours
from publication.
kind regards,
--
Claudiu Costin, claudiuc@...
Linux-KDE Romania http://www.ro.kde.org

Hello Ciaran,
Wednesday, July 23, 2003, 4:57:42 PM, you wrote:
CM> Hi
CM> Has anyone got irda working on a Toshiba TE2100? Its another SMC
CM> LPC47N227.
CM> smcinit does seem to set the irq etc on the controller and smsc-ircc2
CM> loads without error but I cant seem to get anything from it with
CM> irdadump or discovery.
CM> Anyone been here already ?
I have Toshiba Satellite 2405, SMC dont-know-what-kind-of
I could not get it to work. smsc-ircc did not work for me (windows
says it is LPC 248C
--
br
Evgeny
enst@...

Hi
Has anyone got irda working on a Toshiba TE2100? Its another SMC
LPC47N227.
smcinit does seem to set the irq etc on the controller and smsc-ircc2
loads without error but I cant seem to get anything from it with
irdadump or discovery.
Anyone been here already ?
Ciaran

ok, once again a little success i can report:
(i'm on 2.6.0-test1 now, btw)
irda _does_ work now with acpi=off and the smc module (with irq=4) in
sir mode.
it did _not_ work with acpi (on 2.5.75 tho, will reboot right now and
test if it works now, but i'm pessimistic).
something weird, which points to the acpi-initialization is that with
lspnp -v it gives me 'interrupt not configured' for the smc chip. with
acpi=off it shows me the correct irq=4.
i guess it's now up to the smc/acpi folks. any tips?
-h

K.S.Sathish wrote :
>
> Jun 7 22:12:29 130 user.err irattach: ioctl(TIOCGETD): Invalid argument
It looks like the TTY layer is broken on SH4. This is not even
involving the IrDA stack.
The corresponding code is :
------------------------------
if (ioctl(ttyfd, TIOCGETD, &initdisc) < 0) {
syslog(LOG_ERR, "ioctl(TIOCGETD): %m");
clean_exit(-1);
}
------------------------------
This has always worked for me in various platforms, and this
is TTY generic, so you may want to bring that on the SH mailing lists.
Good luck...
Jean

Community

Help

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

CountryState

JavaScript is required for this form.

I agree to receive quotes, newsletters and other information from sourceforge.net and its partners regarding IT services and products. I understand that I can withdraw my consent at any time. Please refer to our Privacy Policy or Contact Us for more details