On Sunday 10 February 2013 at 17:30:47, Wolfram Sang wrote:
> > what happend to this one ? It was a patch updating Kconfig help for
> > at24.
>
> Do you know linux-next? Have a look there...
Thank you for the hint and for commiting it.
Lars
--
To unsubscribe from this list: send the line
On Sunday 10 February 2013 at 17:30:47, Wolfram Sang wrote:
what happend to this one ? It was a patch updating Kconfig help for
at24.
Do you know linux-next? Have a look there...
Thank you for the hint and for commiting it.
Lars
--
To unsubscribe from this list: send the line unsubscribe
> what happend to this one ? It was a patch updating Kconfig help for at24.
Do you know linux-next? Have a look there...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
what happend to this one ? It was a patch updating Kconfig help for at24.
Do you know linux-next? Have a look there...
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Wednesday 05 December 2012 at 17:41:53, Wolfram Sang wrote:
> > > The method of accessing EEPROMs is used by way more chips than FRAMs.
> > > So, I'd prefer to have the text updated more generic like "EEPROMs and
> > > similar devices like RAMs, ROMs, etc...". Describing setting .flags in
> >
On Wednesday 05 December 2012 at 17:41:53, Wolfram Sang wrote:
The method of accessing EEPROMs is used by way more chips than FRAMs.
So, I'd prefer to have the text updated more generic like EEPROMs and
similar devices like RAMs, ROMs, etc Describing setting .flags in
Kconfig is
On Thursday 24 January 2013 at 08:27:01, Wolfram Sang wrote:
> > > > > > I wanted to use a fm24c04 i2c fram chip with linux. I grepped
> > > > > > the source and found nothing. I later found that my chip can be
> > > > > > handled by at24 eeprom driver. It creates a sysfs file called
> > > > > >
On Thursday 24 January 2013 at 08:27:01, Wolfram Sang wrote:
I wanted to use a fm24c04 i2c fram chip with linux. I grepped
the source and found nothing. I later found that my chip can be
handled by at24 eeprom driver. It creates a sysfs file called
eeprom to read from and
On Fri, Dec 07, 2012 at 11:14:28AM +0100, Lars Poeschel wrote:
> > > > > I wanted to use a fm24c04 i2c fram chip with linux. I grepped the
> > > > > source and found nothing. I later found that my chip can be handled
> > > > > by at24 eeprom driver. It creates a sysfs file called eeprom to
> > > >
On Fri, Dec 07, 2012 at 11:14:28AM +0100, Lars Poeschel wrote:
I wanted to use a fm24c04 i2c fram chip with linux. I grepped the
source and found nothing. I later found that my chip can be handled
by at24 eeprom driver. It creates a sysfs file called eeprom to
read from and
> > > > I wanted to use a fm24c04 i2c fram chip with linux. I grepped the
> > > > source and found nothing. I later found that my chip can be handled
> > > > by at24 eeprom driver. It creates a sysfs file called eeprom to
> > > > read from and write to the chip. Userspace has no chance to
> > > >
I wanted to use a fm24c04 i2c fram chip with linux. I grepped the
source and found nothing. I later found that my chip can be handled
by at24 eeprom driver. It creates a sysfs file called eeprom to
read from and write to the chip. Userspace has no chance to
distinguish if it is
Hi,
On Wed, Dec 05, 2012 at 10:43:07AM +0100, Lars Poeschel wrote:
> I see there where to much "no"s to get anything in, but thank you for
> your comments and explanations.
Not necessarily, just not in this form :)
>
> > > I wanted to use a fm24c04 i2c fram chip with linux. I grepped the
I see there where to much "no"s to get anything in, but thank you for
your comments and explanations.
> > I wanted to use a fm24c04 i2c fram chip with linux. I grepped the source
> > and found nothing. I later found that my chip can be handled by at24
> > eeprom driver. It creates a sysfs file
I see there where to much nos to get anything in, but thank you for
your comments and explanations.
I wanted to use a fm24c04 i2c fram chip with linux. I grepped the source
and found nothing. I later found that my chip can be handled by at24
eeprom driver. It creates a sysfs file called
Hi,
On Wed, Dec 05, 2012 at 10:43:07AM +0100, Lars Poeschel wrote:
I see there where to much nos to get anything in, but thank you for
your comments and explanations.
Not necessarily, just not in this form :)
I wanted to use a fm24c04 i2c fram chip with linux. I grepped the source
and
Hi,
> I wanted to use a fm24c04 i2c fram chip with linux. I grepped the source
> and found nothing. I later found that my chip can be handled by at24
> eeprom driver. It creates a sysfs file called eeprom to read from and
> write to the chip. Userspace has no chance to distinguish if it is
>
Hello!
I wanted to use a fm24c04 i2c fram chip with linux. I grepped the source
and found nothing. I later found that my chip can be handled by at24
eeprom driver. It creates a sysfs file called eeprom to read from and
write to the chip. Userspace has no chance to distinguish if it is
writing an
Hello!
I wanted to use a fm24c04 i2c fram chip with linux. I grepped the source
and found nothing. I later found that my chip can be handled by at24
eeprom driver. It creates a sysfs file called eeprom to read from and
write to the chip. Userspace has no chance to distinguish if it is
writing an
Hi,
I wanted to use a fm24c04 i2c fram chip with linux. I grepped the source
and found nothing. I later found that my chip can be handled by at24
eeprom driver. It creates a sysfs file called eeprom to read from and
write to the chip. Userspace has no chance to distinguish if it is
writing
20 matches
Mail list logo
