Re: [Owfs-developers] w1 changes
Am Freitag, 10. März 2006 07:20 schrieb Christoph Scheurer: Do you know how to talk to the i2c via user-space?(Something like libusb or tty system). Then a non-w1 approach would be easy. There is an example implementation for the DS2482 in the kernel; module, and the communication structure is an easy match for OWFS. If you load the i2c_dev module you get /dev/i2c-? device files to communicate with i2c. This is e.g. what sensors-detect from lm-sensors uses. Sorry, that was too unspecific. What I mean is: one could just use an empty I2C-slave module with only the basic I2C communication support that recognizes the DS2482 and move all the W1 specific functions to OWFS. Besides having only a brief look into the w1 kernel code, I think handling the remote chips is a userspace task, like with RS232 host adapter interface in kernelspace and modem/terminal control by a userspace program. In an ideal world, the kernel code should render the differences between i2c, parallel, serial and usb host adapters transparent and enumerate the adapters somewhere in /sys/bus/w1, where they can be symlinked to /dev nodes on demand. The owfs project, in having far more than one access method (fuse, owhttpd, owserver, owtcl etc.) to the onewire, shows the demand for additional user-level control code. There is no way these features will get into the kernel sometime. I'm not into bashing Evgeniy's efforts, but besides from some very low-level applications - like implementing a streamlined battery monitoring interface for both onewire *and other* service processors - the onewire has very little use for the kernel itself. Please tell otherwise, I'd really like to know. I'll think Evgeniy's code can be improved to do other than *iso*chronous polling of remote chips, but I don't think that's the way it should be done. In contrast, it should provide a transparent interface where the onewire discover sequence can be triggered, where alarms are monitored, and where remote chips can be accessed by a user-space library. Kind regards Jan Kandziora -- Williams and Holland's Law: If enough data is collected, anything may be proven by statistical methods. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] w1 changes
Am Freitag, 10. März 2006 12:43 schrieb Christoph Scheurer: Sorry, that was too unspecific. What I mean is: one could just use an empty I2C-slave module with only the basic I2C communication support that recognizes the DS2482 and move all the W1 specific functions to OWFS. Besides having only a brief look into the w1 kernel code, I think handling the remote chips is a userspace task, like with RS232 host adapter interface in kernelspace and modem/terminal control by a userspace program. That is exactly what I had in mind. The DS2482 is an I2C slave, so you have a kernel module for the DS2482 which only recognizes the chip as an I2C slave and attaches it to the I2C master (whatever that is in your application: on-board, in-chip, parallel, serial, ...). Then you can communicate to the DS2482 through opening the /dev/i2c-? that represents the I2C-bus on which your DS2482 is attached the same way as you talk to a serial 1-wire adapter through /dev/ttyS? . The only complication (which is more like the USB case) is that now you have to explicitly include the I2C-address of your DS2482 since there can be multiple DS2482 on any I2C-bus. Hm, I like parts of Evgeniy's approach. The way you describe it i2c-Onewire hosts would not be transparent against e.g. rs232-Onewire hosts. To fix my position: I think it's best to have a generic w1 kernel interface like the generic usb, serial or parport driver. But I'll think Evgeniy already implemented that. All additional interfacing should be doen in userland. Kind regards Jan -- It's no wonder they call it WinNT; WNT = VMS++ --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] w1 changes
What should the command line interface look like? owfs /dev/i2c-?/address Seems good, the address would be an integer between 0-127 for the standard 7-Bit I2C-addresses? The 10-Bit addresses are included in the I2C standard but the kernel support is only experimental since no known I2C devices with 10-Bit addresses are known yet. Christoph -- Christoph Scheurer GnuPG key Id: 0x6128C6B6 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] w1 changes
What should the command line interface look like? owfs /dev/i2c-?/address Just a suggestion concerning the internal structure of such an adapter: If you look at Documentation/i2c/smbus-protocol it seems to be better to implement it only using the SMBus subset of the I2C protocol, if at all possible. Otherwise owfs would have to check whether the /dev/i2c-? device really supports the full I2C protocol (see Documentation/i2c/functionality ). The advantage I see with implementing the adapter based on the SMBus protocol is, that most motherboards contain SMBus controllers that are supported by the I2C subsystem. You can get access to theses buses e.g. off of SDRAM modules (see http://www.madhacker.org/locate_smbus.htm ) and the DS2482 could be easily (internally) attached to any PC. Christoph -- Christoph Scheurer GnuPG key Id: 0x6128C6B6 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] w1 changes
Am Mittwoch, 8. März 2006 06:18 schrieb Paul Alfille: Just a progress report: After extensive discussions with Evgeniy Polyakov, it looks like OWFS will be able to use the linux kernel 1-wire drivers as a possible 1-wire adapter source. 1. The current w1 supports i2c adapters 2804-x00, which is not supported by OWFS natively. I've been interested in OWFS support for the I2C host adapter (DS2482-x00) device for some time now. As I figured out now, I2C-Onewire this would be the better solution for the vending machine I develop than USB or serial as the embedded board we will use has I2C on its connectors. Do you expect major difficulties to implement I2C-Onewire? I could even think of sponsoring this development task if the device is at least as performant as the USB host adapter and is ready on time (--6..8 weeks). Goal would be support for the DS2482-800 chip. (Please don't expect too much money, my budget is limited, too) Kind regards Jan Kandziora -- The first law of demos: - never try to actually use the system for anything --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
RE: [Owfs-developers] w1 changes
Jan, the only support needed would be either a sample of the hardware (adapter) or the willingness to test frequent test builds. The only changes will be that the w1 polls at it's own rate rather than on demand, and that multiple adapters aren't yet supported by w1. Also the alarm directory isn't yet implemented. Evgeniy is eager to improve function. Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jan Kandziora Sent: Thursday, March 09, 2006 2:59 AM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] w1 changes Am Mittwoch, 8. März 2006 06:18 schrieb Paul Alfille: Just a progress report: After extensive discussions with Evgeniy Polyakov, it looks like OWFS will be able to use the linux kernel 1-wire drivers as a possible 1-wire adapter source. 1. The current w1 supports i2c adapters 2804-x00, which is not supported by OWFS natively. I've been interested in OWFS support for the I2C host adapter (DS2482-x00) device for some time now. As I figured out now, I2C-Onewire this would be the better solution for the vending machine I develop than USB or serial as the embedded board we will use has I2C on its connectors. Do you expect major difficulties to implement I2C-Onewire? I could even think of sponsoring this development task if the device is at least as performant as the USB host adapter and is ready on time (--6..8 weeks). Goal would be support for the DS2482-800 chip. (Please don't expect too much money, my budget is limited, too) Kind regards Jan Kandziora -- The first law of demos: - never try to actually use the system for anything --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] w1 changes
Am Donnerstag, 9. März 2006 12:53 schrieb Alfille, Paul H.,M.D.: Jan, the only support needed would be either a sample of the hardware (adapter) or the willingness to test frequent test builds. I will definately build a board based on the DS2482-800 chip and will test owfs improvements, too. The only changes will be that the w1 polls at it's own rate rather than on demand, Hm. That's not so good. If one has a lot of chips on the bus, but only a few of them used at the same time, synchronous polling makes thing things damn slow. But that's exactly my use case. I could release a developer for this in ~8..10 weeks I think, but that's too late for my current development. Maybe the best idea for me is to put space for both DS2480B and DS2482-800 on my PCB and improve later. ^^; and that multiple adapters aren't yet supported by w1. Not that important for me, I think. Also the alarm directory isn't yet implemented. Evgeniy is eager to improve function. I'll talk to him directly, too. Kind regards Jan Kandziora -- Linux - It's now safe to turn on your computer. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
