On 24.10.2018 01:31, Lukasz Majewski wrote:
> Hi Martin, Eugen,
>
>> On 23/10/18 10:40, eugen.hris...@microchip.com wrote:
>>>
>>> I tried as much as possible to decouple the W1 bus from the W1
>>> EEPROM memories. It is possible that we will have a different
>>> framework for EEPROMs that will
Hi Martin, Eugen,
> On 23/10/18 10:40, eugen.hris...@microchip.com wrote:
> >
> > I tried as much as possible to decouple the W1 bus from the W1
> > EEPROM memories. It is possible that we will have a different
> > framework for EEPROMs that will include both 1wire and i2c eeproms,
> > and then th
On 23/10/18 10:40, eugen.hris...@microchip.com wrote:
I tried as much as possible to decouple the W1 bus from the W1 EEPROM
memories. It is possible that we will have a different framework for
EEPROMs that will include both 1wire and i2c eeproms, and then the
interfacing would be pretty easy to
On 23.10.2018 11:31, Martin Fuzzey wrote:
> On 23/10/18 09:07, eugen.hris...@microchip.com wrote:
>>
>> On 22.10.2018 19:51, Martin Fuzzey wrote:
>>> Building with CONFIG_W1 and CONFIG_CMD_W1 but without CONFIG_W1_EEPROM
>>> fails with
>>> drivers/w1/w1-uclass.c:104: undefined reference to
>
On 23/10/18 09:07, eugen.hris...@microchip.com wrote:
On 22.10.2018 19:51, Martin Fuzzey wrote:
Building with CONFIG_W1 and CONFIG_CMD_W1 but without CONFIG_W1_EEPROM
fails with
drivers/w1/w1-uclass.c:104: undefined reference to
`w1_eeprom_register_new_device'
cmd/w1.c:93: unde
On 22.10.2018 19:51, Martin Fuzzey wrote:
> Building with CONFIG_W1 and CONFIG_CMD_W1 but without CONFIG_W1_EEPROM
> fails with
> drivers/w1/w1-uclass.c:104: undefined reference to
> `w1_eeprom_register_new_device'
> cmd/w1.c:93: undefined reference to `w1_eeprom_read_buf'
>
> Fix t
Building with CONFIG_W1 and CONFIG_CMD_W1 but without CONFIG_W1_EEPROM
fails with
drivers/w1/w1-uclass.c:104: undefined reference to
`w1_eeprom_register_new_device'
cmd/w1.c:93: undefined reference to `w1_eeprom_read_buf'
Fix this.
Signed-off-by: Martin Fuzzey
---
cmd/w1.c
7 matches
Mail list logo