On Fri, Jul 13, 2007 at 12:41:14AM +0200, Pavel Machek wrote:
> Hi!
>
> > > > +The kernel exported sysfs exports internal kernel
> > > > implementation-details
> > > > +and depends on internal kernel structures and layout. It is agreed upon
> > > > +by the kernel developers that the Linux kernel
Hi!
> > > +The kernel exported sysfs exports internal kernel implementation-details
> > > +and depends on internal kernel structures and layout. It is agreed upon
> > > +by the kernel developers that the Linux kernel does not provide a stable
> > > +internal API. As sysfs is a direct export of
On Thu, Jul 12, 2007 at 10:48:46AM +0200, Pavel Machek wrote:
> On Wed 2007-07-11 16:31:20, Greg Kroah-Hartman wrote:
> > From: Kay Sievers <[EMAIL PROTECTED]>
> >
> > Here's a document to help clear things up.
> >
> > Signed-off-by: Kay Sievers <[EMAIL PROTECTED]>
> > Signed-off-by: Greg
On Thu, 2007-07-12 at 10:48 +0200, Pavel Machek wrote:
> On Wed 2007-07-11 16:31:20, Greg Kroah-Hartman wrote:
> > From: Kay Sievers <[EMAIL PROTECTED]>
> >
> > Here's a document to help clear things up.
> >
> > Signed-off-by: Kay Sievers <[EMAIL PROTECTED]>
> > Signed-off-by: Greg Kroah-Hartman
On Wed 2007-07-11 16:31:20, Greg Kroah-Hartman wrote:
> From: Kay Sievers <[EMAIL PROTECTED]>
>
> Here's a document to help clear things up.
>
> Signed-off-by: Kay Sievers <[EMAIL PROTECTED]>
> Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
> ---
> Documentation/sysfs-rules.txt | 166
>
On 07/12/2007 01:43 AM, Greg KH wrote:
Patches for grammer are always accepted :)
--- a 2007-07-12 12:36:42.0 +0200
+++ b 2007-07-12 12:36:48.0 +0200
@@ -1 +1 @@
-Patches for grammer are always accepted :)
+Patches for grammar are always accepted :)
Rene.
-
To
On 07/12/2007 01:43 AM, Greg KH wrote:
Patches for grammer are always accepted :)
--- a 2007-07-12 12:36:42.0 +0200
+++ b 2007-07-12 12:36:48.0 +0200
@@ -1 +1 @@
-Patches for grammer are always accepted :)
+Patches for grammar are always accepted :)
Rene.
-
To
On Wed 2007-07-11 16:31:20, Greg Kroah-Hartman wrote:
From: Kay Sievers [EMAIL PROTECTED]
Here's a document to help clear things up.
Signed-off-by: Kay Sievers [EMAIL PROTECTED]
Signed-off-by: Greg Kroah-Hartman [EMAIL PROTECTED]
---
Documentation/sysfs-rules.txt | 166
On Thu, 2007-07-12 at 10:48 +0200, Pavel Machek wrote:
On Wed 2007-07-11 16:31:20, Greg Kroah-Hartman wrote:
From: Kay Sievers [EMAIL PROTECTED]
Here's a document to help clear things up.
Signed-off-by: Kay Sievers [EMAIL PROTECTED]
Signed-off-by: Greg Kroah-Hartman [EMAIL
On Thu, Jul 12, 2007 at 10:48:46AM +0200, Pavel Machek wrote:
On Wed 2007-07-11 16:31:20, Greg Kroah-Hartman wrote:
From: Kay Sievers [EMAIL PROTECTED]
Here's a document to help clear things up.
Signed-off-by: Kay Sievers [EMAIL PROTECTED]
Signed-off-by: Greg Kroah-Hartman [EMAIL
Hi!
+The kernel exported sysfs exports internal kernel implementation-details
+and depends on internal kernel structures and layout. It is agreed upon
+by the kernel developers that the Linux kernel does not provide a stable
+internal API. As sysfs is a direct export of kernel
On Fri, Jul 13, 2007 at 12:41:14AM +0200, Pavel Machek wrote:
Hi!
+The kernel exported sysfs exports internal kernel
implementation-details
+and depends on internal kernel structures and layout. It is agreed upon
+by the kernel developers that the Linux kernel does not provide
On Wed, Jul 11, 2007 at 07:38:59PM -0400, Robert P. J. Day wrote:
> On Wed, 11 Jul 2007, Greg Kroah-Hartman wrote:
>
> > From: Kay Sievers <[EMAIL PROTECTED]>
> >
> > Here's a document to help clear things up.
> >
> > Signed-off-by: Kay Sievers <[EMAIL PROTECTED]>
> > Signed-off-by: Greg
On Wed, 11 Jul 2007, Greg Kroah-Hartman wrote:
> From: Kay Sievers <[EMAIL PROTECTED]>
>
> Here's a document to help clear things up.
>
> Signed-off-by: Kay Sievers <[EMAIL PROTECTED]>
> Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
> ---
> Documentation/sysfs-rules.txt | 166
>
From: Kay Sievers <[EMAIL PROTECTED]>
Here's a document to help clear things up.
Signed-off-by: Kay Sievers <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
Documentation/sysfs-rules.txt | 166 +
1 files changed, 166
From: Kay Sievers [EMAIL PROTECTED]
Here's a document to help clear things up.
Signed-off-by: Kay Sievers [EMAIL PROTECTED]
Signed-off-by: Greg Kroah-Hartman [EMAIL PROTECTED]
---
Documentation/sysfs-rules.txt | 166 +
1 files changed, 166 insertions(+),
On Wed, 11 Jul 2007, Greg Kroah-Hartman wrote:
From: Kay Sievers [EMAIL PROTECTED]
Here's a document to help clear things up.
Signed-off-by: Kay Sievers [EMAIL PROTECTED]
Signed-off-by: Greg Kroah-Hartman [EMAIL PROTECTED]
---
Documentation/sysfs-rules.txt | 166
On Wed, Jul 11, 2007 at 07:38:59PM -0400, Robert P. J. Day wrote:
On Wed, 11 Jul 2007, Greg Kroah-Hartman wrote:
From: Kay Sievers [EMAIL PROTECTED]
Here's a document to help clear things up.
Signed-off-by: Kay Sievers [EMAIL PROTECTED]
Signed-off-by: Greg Kroah-Hartman [EMAIL
On Monday 25 June 2007 10:57:35 Kay Sievers wrote:
> > > Sure, all devices have a "subsystem" link, you have to readlink()
> > > that, and if it ends in "block, you have a blockdev. But as mentioned
> > > in an earlier mail, you should stop scanning /sys/devices/ and always
> > > come from the
On 6/24/07, Rob Landley <[EMAIL PROTECTED]> wrote:
On Sunday 24 June 2007 07:03:39 Kay Sievers wrote:
> On 6/24/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> > On Saturday 23 June 2007 08:49:47 Kay Sievers wrote:
> > > On 6/22/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> > > > On Friday 08 June
On 6/24/07, Rob Landley [EMAIL PROTECTED] wrote:
On Sunday 24 June 2007 07:03:39 Kay Sievers wrote:
On 6/24/07, Rob Landley [EMAIL PROTECTED] wrote:
On Saturday 23 June 2007 08:49:47 Kay Sievers wrote:
On 6/22/07, Rob Landley [EMAIL PROTECTED] wrote:
On Friday 08 June 2007 16:36:37
On Monday 25 June 2007 10:57:35 Kay Sievers wrote:
Sure, all devices have a subsystem link, you have to readlink()
that, and if it ends in block, you have a blockdev. But as mentioned
in an earlier mail, you should stop scanning /sys/devices/ and always
come from the subsystem
On Sunday 24 June 2007 07:03:39 Kay Sievers wrote:
> On 6/24/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> > On Saturday 23 June 2007 08:49:47 Kay Sievers wrote:
> > > On 6/22/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> > > > On Friday 08 June 2007 16:36:37 Greg KH wrote:
> > > > > Over time there
On 6/24/07, Rob Landley <[EMAIL PROTECTED]> wrote:
On Saturday 23 June 2007 08:49:47 Kay Sievers wrote:
> On 6/22/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> > On Friday 08 June 2007 16:36:37 Greg KH wrote:
> > > Over time there have been a number of problems when sysfs has changed
> > > in
On 6/24/07, Rob Landley [EMAIL PROTECTED] wrote:
On Saturday 23 June 2007 08:49:47 Kay Sievers wrote:
On 6/22/07, Rob Landley [EMAIL PROTECTED] wrote:
On Friday 08 June 2007 16:36:37 Greg KH wrote:
Over time there have been a number of problems when sysfs has changed
in unexpected ways.
On Sunday 24 June 2007 07:03:39 Kay Sievers wrote:
On 6/24/07, Rob Landley [EMAIL PROTECTED] wrote:
On Saturday 23 June 2007 08:49:47 Kay Sievers wrote:
On 6/22/07, Rob Landley [EMAIL PROTECTED] wrote:
On Friday 08 June 2007 16:36:37 Greg KH wrote:
Over time there have been a number
On Saturday 23 June 2007 08:49:47 Kay Sievers wrote:
> On 6/22/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> > On Friday 08 June 2007 16:36:37 Greg KH wrote:
> > > Over time there have been a number of problems when sysfs has changed
> > > in "unexpected" ways. Here's a document that Kay wrote a
On 6/22/07, Rob Landley <[EMAIL PROTECTED]> wrote:
On Friday 08 June 2007 16:36:37 Greg KH wrote:
> Over time there have been a number of problems when sysfs has changed in
> "unexpected" ways. Here's a document that Kay wrote a while ago that
> I'd like to add to the kernel Documentation
On 6/22/07, Rob Landley [EMAIL PROTECTED] wrote:
On Friday 08 June 2007 16:36:37 Greg KH wrote:
Over time there have been a number of problems when sysfs has changed in
unexpected ways. Here's a document that Kay wrote a while ago that
I'd like to add to the kernel Documentation directory to
On Saturday 23 June 2007 08:49:47 Kay Sievers wrote:
On 6/22/07, Rob Landley [EMAIL PROTECTED] wrote:
On Friday 08 June 2007 16:36:37 Greg KH wrote:
Over time there have been a number of problems when sysfs has changed
in unexpected ways. Here's a document that Kay wrote a while ago
On Friday 08 June 2007 16:36:37 Greg KH wrote:
> Over time there have been a number of problems when sysfs has changed in
> "unexpected" ways. Here's a document that Kay wrote a while ago that
> I'd like to add to the kernel Documentation directory to help userspace
> programmers out.
>
> Any
On Friday 08 June 2007 16:36:37 Greg KH wrote:
Over time there have been a number of problems when sysfs has changed in
unexpected ways. Here's a document that Kay wrote a while ago that
I'd like to add to the kernel Documentation directory to help userspace
programmers out.
Any comments or
On Sun, 2007-06-10 at 09:56 -0700, Randy Dunlap wrote:
> On Sun, 10 Jun 2007 10:02:00 -0400 Theodore Tso wrote:
>
> > On Fri, Jun 08, 2007 at 01:36:37PM -0700, Greg KH wrote:
> > > The kernel exported sysfs exports internal kernel implementation-details
> > > and depends on internal
On Sun, 10 Jun 2007 10:02:00 -0400 Theodore Tso wrote:
> On Fri, Jun 08, 2007 at 01:36:37PM -0700, Greg KH wrote:
> > The kernel exported sysfs exports internal kernel implementation-details
> > and depends on internal kernel-structures and layout. It is agreed upon
> > kernel developers, that
On Fri, Jun 08, 2007 at 01:36:37PM -0700, Greg KH wrote:
> The kernel exported sysfs exports internal kernel implementation-details
> and depends on internal kernel-structures and layout. It is agreed upon
> kernel developers, that the Linux kernel does not provide a stable
> internal API. As
On Fri, Jun 08, 2007 at 01:36:37PM -0700, Greg KH wrote:
The kernel exported sysfs exports internal kernel implementation-details
and depends on internal kernel-structures and layout. It is agreed upon
kernel developers, that the Linux kernel does not provide a stable
internal API. As sysfs
On Sun, 10 Jun 2007 10:02:00 -0400 Theodore Tso wrote:
On Fri, Jun 08, 2007 at 01:36:37PM -0700, Greg KH wrote:
The kernel exported sysfs exports internal kernel implementation-details
and depends on internal kernel-structures and layout. It is agreed upon
kernel developers, that the Linux
On Sun, 2007-06-10 at 09:56 -0700, Randy Dunlap wrote:
On Sun, 10 Jun 2007 10:02:00 -0400 Theodore Tso wrote:
On Fri, Jun 08, 2007 at 01:36:37PM -0700, Greg KH wrote:
The kernel exported sysfs exports internal kernel implementation-details
and depends on internal kernel-structures and
On 08/06/07, Greg KH <[EMAIL PROTECTED]> wrote:
Over time there have been a number of problems when sysfs has changed in
"unexpected" ways. Here's a document that Kay wrote a while ago that
I'd like to add to the kernel Documentation directory to help userspace
programmers out.
Any comments or
On 6/9/07, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote:
Greg KH wrote:
> - Do not use libsysfs
> It makes assumptions about sysfs which are not true. Its API does not
> offer any abstraction, it exposes all the kernel driver-core
> implementation details in its own API. Therefore it is
Greg KH wrote:
- Do not use libsysfs
It makes assumptions about sysfs which are not true. Its API does not
offer any abstraction, it exposes all the kernel driver-core
implementation details in its own API. Therefore it is not better than
reading directories and opening the files
On Jun 8 2007 13:36, Greg KH wrote:
>
>Any comments or critique of this is greatly appreciated.
>
>
>
>Rules to access device-information in the Linux kernel sysfs
>
>The kernel exported sysfs exports internal kernel implementation-details
>and depends on
On Jun 8 2007 13:36, Greg KH wrote:
Any comments or critique of this is greatly appreciated.
Rules to access device-information in the Linux kernel sysfs
The kernel exported sysfs exports internal kernel implementation-details
and depends on internal
Greg KH wrote:
- Do not use libsysfs
It makes assumptions about sysfs which are not true. Its API does not
offer any abstraction, it exposes all the kernel driver-core
implementation details in its own API. Therefore it is not better than
reading directories and opening the files
On 6/9/07, Alexander E. Patrakov [EMAIL PROTECTED] wrote:
Greg KH wrote:
- Do not use libsysfs
It makes assumptions about sysfs which are not true. Its API does not
offer any abstraction, it exposes all the kernel driver-core
implementation details in its own API. Therefore it is not
On 08/06/07, Greg KH [EMAIL PROTECTED] wrote:
Over time there have been a number of problems when sysfs has changed in
unexpected ways. Here's a document that Kay wrote a while ago that
I'd like to add to the kernel Documentation directory to help userspace
programmers out.
Any comments or
Over time there have been a number of problems when sysfs has changed in
"unexpected" ways. Here's a document that Kay wrote a while ago that
I'd like to add to the kernel Documentation directory to help userspace
programmers out.
Any comments or critique of this is greatly appreciated.
thanks,
Over time there have been a number of problems when sysfs has changed in
unexpected ways. Here's a document that Kay wrote a while ago that
I'd like to add to the kernel Documentation directory to help userspace
programmers out.
Any comments or critique of this is greatly appreciated.
thanks,
48 matches
Mail list logo
