Wolfgang Grandegger wrote:
> Paul Alfille wrote:
>> On Thu, Dec 3, 2009 at 8:09 AM, Wolfgang Grandegger
>> wrote:
>>
>>> This could happen because the address of the bus_master variable
>>> was pointing to a stack location of the initiating function.
>>> The problem is fixes by passing the value o
Paul Alfille wrote:
> On Thu, Dec 3, 2009 at 8:12 AM, Wolfgang Grandegger
> wrote:
>
>> Paul Alfille wrote:
>>> No, the Dallas filesystem (embedded into the rather small memory of their
>>> chips) is distinct from OWFS.
>> OK, do you (or anybody else) know of any program allowing to interpret
>>
Paul Alfille wrote:
> On Thu, Dec 3, 2009 at 8:09 AM, Wolfgang Grandegger
> wrote:
>
>> This could happen because the address of the bus_master variable
>> was pointing to a stack location of the initiating function.
>> The problem is fixes by passing the value of bus_master as
>> argument.
>>
>>
It should work with any bus master, since it's a modification (extension) of
the 1-wire protocol. I'll did mine out and test.
Paul Alfille
On Wed, Dec 2, 2009 at 9:54 AM, Michael Markstaller wrote:
> Hi,
>
> while playing around with a LinkLocator, just a quick question:
> Is this supposed to w
Ok, let's be systematic.
What are the differences between the new installation the the existing
successful ones?
Paul
On Tue, Dec 1, 2009 at 5:07 PM, Jim Kusznir wrote:
> Unfortunately, that was one of the first things I tried...I did not
> have any kernel modules ds* or *onewire* loaded anywh
Both patches applied!
Paul Alfille
On Wed, Dec 2, 2009 at 5:26 PM, Ilya Pravdivtsev wrote:
> I am not sure if it is the best way, but maybe use sed?
> Patch attached.
>
> Ilya.
>
>
--
Join us December 9, 2009 for the Red
On Thu, Dec 3, 2009 at 8:09 AM, Wolfgang Grandegger wrote:
> This could happen because the address of the bus_master variable
> was pointing to a stack location of the initiating function.
> The problem is fixes by passing the value of bus_master as
> argument.
>
>
Very nice. A pretty subtle bug,
On Thu, Dec 3, 2009 at 8:12 AM, Wolfgang Grandegger wrote:
> Paul Alfille wrote:
> > No, the Dallas filesystem (embedded into the rather small memory of their
> > chips) is distinct from OWFS.
>
> OK, do you (or anybody else) know of any program allowing to interpret
> such data and present it to
Hi,
I have a machine in the owfs hung state right now (9 am PST 12/03). I have
run a strace on an ls command, which exhibits the behavior, if that is of
any use.
I can keep he machine in the hung state for about another hour, before I
need to reboot. If there are any commands that I can run to he
Paul Alfille wrote:
> The w1 kernel module is used by owfs like a physical bus master. The match
> is not exact, so the workarounds are interesting.
>
> 1. w1 grabs all the bus masters it supports. They get no particular order,
> and if disconnected, the bus master is re-announced with a new locat
Paul Alfille wrote:
> No, the Dallas filesystem (embedded into the rather small memory of their
> chips) is distinct from OWFS.
OK, do you (or anybody else) know of any program allowing to interpret
such data and present it to the user via file-system?
> OWFS is a way of making the entire 1-wire
This could happen because the address of the bus_master variable
was pointing to a stack location of the initiating function.
The problem is fixes by passing the value of bus_master as
argument.
Signed-off-by: Wolfgang Grandegger
---
This fixes one problem. Now I'm facing another one with "owfs"
No, the Dallas filesystem (embedded into the rather small memory of their
chips) is distinct from OWFS.
OWFS is a way of making the entire 1-wire bus be a virttual fil;esystem,
with uniquely numbered devices be directories and each property (like memory
or temperature) be a file.
That same design
Hello,
1-wire and OWFS is quite new to me. I'm a bit confused about the usage
of the name OWFS. There is a document from Dallas/Maxim,
http://pdfserv.maxim-ic.com/en/an/AN114.pdf,
describing OWFS, which provides a directory structure for data residing
in 1-wire devices. What is the relation to
14 matches
Mail list logo