Actually, you are giving an excellent illustration of the obscure code in
that part.
I was going through and had the same thought process -- am trying to clean
it up a bit.
Paul
On 8/25/07, Christian Magnusson <[EMAIL PROTECTED]> wrote:
>
>
>
> I guess I'm too tired… I noticed in->Adapter was set in DS2480_reset()
>
> pn->in->Adapter = (buf & RB_CHIPID_MASK) >> 2;
>
>
>
> and I guess you can ignore my two last posts… dohhh…
>
>
>
> /Christian
>
>
>
>
>
>
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Christian
> Magnusson
> *Sent:* den 25 augusti 2007 14:06
> *To:* [email protected]
> *Subject:* Re: [Owfs-developers] Problem with BR6104KP and OWFS
>
>
>
> I mean, the switch-statement in DS2480_detect(), will always return
> –ENODEV since in->Adapter will never be adapter_DS9097U or adapter_DS9097U2
> .
>
>
>
> switch (in->Adapter) {
>
> case adapter_DS9097U2:
>
> case adapter_DS9097U:
>
> in->adapter_name = "DS9097U";
>
> break;
>
> case adapter_LINK:
>
> case adapter_LINK_10:
>
> case adapter_LINK_11:
>
> case adapter_LINK_12:
>
> in->adapter_name = "LINK(emulate mode)";
>
> break;
>
> default:
>
> return -ENODEV;
>
> }
>
>
>
>
>
>
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Christian
> Magnusson
> *Sent:* den 25 augusti 2007 13:36
> *To:* [email protected]
> *Subject:* Re: [Owfs-developers] Problem with BR6104KP and OWFS
>
>
>
> I found another bug I think… The passive adapter adapter_DS9097U is NEVER
> set or used… Seems to be a bug in ow_opt.c
>
> or owlib.c where it first tries DS2480_detect() and then DS9097_detect()
> without changing in->Adapter.
>
>
>
> [EMAIL PROTECTED] owfs]# grep adapter_DS9097 module/owlib/src/c/*.c
> module/owlib/src/include/*.h
>
> module/owlib/src/c/ow_ds9097.c: in->Adapter = adapter_DS9097;
>
> module/owlib/src/c/ow_ds9097U.c: case adapter_DS9097U2:
>
> module/owlib/src/c/ow_ds9097U.c: case adapter_DS9097U:
>
> *module/owlib/src/c/ow_opt.c: in->Adapter = adapter_DS9097; //
> default serial adapter -- the passive one*
>
> *module/owlib/src/c/ow_opt.c: in->Adapter = adapter_DS9097; //
> passive adapter*
>
> module/owlib/src/include/ow_connection.h: adapter_DS9097 = 0,
>
> module/owlib/src/include/ow_connection.h: adapter_DS9097U2 = 2,
>
> module/owlib/src/include/ow_connection.h: adapter_DS9097U = 3,
>
>
>
> That explains the problem "nattugglan" has….
> http://forum.openwrt.org/viewtopic.php?pid=54362#p54362
>
> With his USB->serial-adapter. (which works with digitemp_9097)
>
>
>
> Can you look at the code Paul… I don't want to break that "HA3" & "HA4B"
> code. Is it only OW_ArgSerial which should be changed?
>
>
>
> static int OW_ArgSerial(const char *arg)
>
> {
>
> struct connection_in *in = NewIn(NULL);
>
> if (in == NULL)
>
> return 1;
>
> in->name = strdup(arg);
>
> in->busmode = bus_serial;
>
> * in->Adapter = adapter_DS9097U;*
>
> * in->adapter_name = "DS9097U";*
>
> return 0;
>
> }
>
>
>
> /Christian
>
>
>
>
>
>
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Paul Alfille
> *Sent:* den 25 augusti 2007 12:51
> *To:* [email protected]
> *Subject:* Re: [Owfs-developers] Problem with BR6104KP and OWFS
>
>
>
>
>
> On 8/25/07, *Christian Magnusson* <[EMAIL PROTECTED]> wrote:
>
>
>
> In /usr/include/linux/stat.h I have these defines….
>
> #define S_IFCHR 0020000
>
> #define S_ISCHR(m) (((m) & S_IFMT) == S_IFCHR)
>
>
>
> The macro is called S_ISCHR(), so I don't think there are anything wrong
> in the source…. Or?
>
>
> That explains why this "bug" hasm't triggered lots of reports.
>
> Ok Vladamir, can you make sure that the devices are really in /dev ? I
> presume your shell prompt doesn't show the current path.
>
> Paul Alfille
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
