Hello!
We've gone all over this many times before. I know, I started a thread
and watched it evolve past its prime, but it seems to have surfaced
yet again.
On the RJ11 PDF that Maxim-IC/Dallas has prepared, (and is available
there someplace) it describes which two wires are chosen as the
One-Wire
Presumably, the reason you are using chaining is so that you don't have to
deal with device IDs. So one natural way to interface a chain is to make a
"chain" directory and put the chained devices inside it, named "0", "1",
"2", ... This way the order of the chain is naturally established by the
a
On 8/1/07, Matthias Urlichs <[EMAIL PROTECTED]> wrote:
>
>
> Why commas? I'd use newlines, they're much more convenient for
> sequential reading from script languages as well as C.
There's that CR vs LF/CR problem between platforms
> 3. Put the "chain" file under "simultaneous -- already a per-s
Hi,
Paul Alfille:
> The new DS28EA00 is a temperature chip that has a special "chain" mode to
> tell location. Specifically there are in/out pins that tell which chip is
> connected to which.
>
Nice. Remind me to beat myself up because the wiring I've been using
definitely doesn't have a spare wi
The new DS28EA00 is a temperature chip that has a special "chain" mode to
tell location. Specifically there are in/out pins that tell which chip is
connected to which.
The description of chaining is at
http://pdfserv.maxim-ic.com/en/an/AN4037.pdf
and the DS28EA00 is at http://datasheets.maxim-ic.c
Am Mittwoch, 1. August 2007 14:41 schrieb Matthias Urlichs:
> Hi,
>
> Jan Kandziora:
> > I specifically think of onewire chips built into laptop batteries. As
> > soon a user encounters such a device, wants to monitor it through the
> > usual kernel hardware monitoring interfaces *and* connects som
Hi,
Jan Kandziora:
> I specifically think of onewire chips built into laptop batteries. As soon a
> user encounters such a device, wants to monitor it through the usual kernel
> hardware monitoring interfaces *and* connects some devices to the laptop
> through owfs (e.g. servicing my vending ma
Am Mittwoch, 1. August 2007 12:58 schrieb Paul Alfille:
>
> So that is the status of the w1 interface. It's very linux-specific, and
> even at best won't add any new function. I was more interested before we
> managed to get I2C working, since there is a kernel module for that as
> well.
>
> In sho
I haven't talked with Evgeniy recently, but did correspond extensively in
the past.
The W1 module polls the DS9490R at (I think) 1 second intervals to update
the temperature readings. Unfortunately it steals the entire 1-wire bus.
There were several solutions:
1. Remove DS9490R (rmmod ds9490r). Y
Am Mittwoch, 1. August 2007 08:21 schrieb Matthias Urlichs:
>
> The simple solution is to blacklist the module (and/or unload it before
> starting owserver) -- and ask your distro not to compile that module by
> default. I have no idea if anybody uses it; it doesn't even support
> hubs.
>
Well, fro
10 matches
Mail list logo
