[PATCH] Correct wording in config COMPILE_TEST

[PATCH] Correct wording in config COMPILE_TEST

[Nick Warne]

Hi All,

A small patch to correct English grammar usage.

Signed-off-by: Nick Warne <nick@linicks.net>


--- linux-3.12-rc1/init/Kconfig	2013-09-16 21:17:51.000000000 +0100
+++ linux-3.12-rc1/init/Kconfignew	2013-09-20 20:46:57.730316831 +0100
@@ -54,18 +54,19 @@
 	  directory to select the cross-compiler automatically.
 
 config COMPILE_TEST
-	bool "Compile also drivers which will not load"
+	bool "Also build drivers which will not load on this platform"
 	default n
 	help
 	  Some drivers can be compiled on a different platform than they are
-	  intended to be run on. Despite they cannot be loaded there (or even
-	  when they load they cannot be used due to missing HW support),
-	  developers still, opposing to distributors, might want to build such
-	  drivers to compile-test them.
+	  intended to be run on. Despite the fact they cannot be loaded (or
+	  even when they load they cannot be used due to missing HW
+	  support etc.), developers, differing from distributors, may need 
+	  to build such drivers to compile-test them.
 
 	  If you are a developer and want to build everything available, say Y
 	  here. If you are a user/distributor, say N here to exclude useless
-	  drivers to be distributed.
+	  drivers to be distributed.  (P.S. no drivers are useless unless you
+	  need them for testing).
 
 config LOCALVERSION
 	string "Local version - append to kernel release"


Nick
-- 
http://linicks.net/

Samsung laptop - missing documentation

[Nick Warne]

running 3.11.12-rc1, config help refers:

Documentation/ABI/testing/sysfs-driver-samsung-laptop

But this is now missing - by design? but I can't find any patch that removed it.

Nick
-- 
http://linicks.net/

IGNORE_THIS Re: Samsung laptop - missing documentation

[Nick Warne]

On Sun, Sep 22, 2013 at 11:40:23AM +0100, Nick Warne wrote:
> running 3.11.12-rc1, config help refers:

Errr 3.12-rc1

And it's there anyway - my FAULT

Sorry for the noise.
> Documentation/ABI/testing/sysfs-driver-samsung-laptop
> 
> But this is now missing - by design? but I can't find any patch that removed it.

Nick
-- 
http://linicks.net/

Re: Samsung laptop - missing documentation

[Borislav Petkov]

On Sun, Sep 22, 2013 at 11:40:23AM +0100, Nick Warne wrote:
> running 3.11.12-rc1, config help refers:
> 
> Documentation/ABI/testing/sysfs-driver-samsung-laptop
> 
> But this is now missing - by design? but I can't find any patch that removed it.

You mean this one:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/ABI/testing/sysfs-driver-samsung-laptop


It is there, maybe check your repo?

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

Samsung N145 Plus lid state issue on sleep

[Nick Warne]

Hi all,

I have a strange problem, which has been on going on for ages, and I finally decided to look at it (as it is a pain in the arse).

Brief details:

Samsung N145 Plus running Slack 14 with handbuilt kernel
Kernel: Linux 3.11.1 #3 SMP Mon Sep 23 19:09:00 BST 2013 i686 Intel(R) Atom(TM) CPU N455   @ 1.66GHz GenuineIntel GNU/Linux
I have no modules built in (.config on request if it helps).

This issue also happened with 'distro' kernel builds... so either it is BIOS issue or hardware fault.  But just in case:

Boot laptop into console - no X - so running pure acpi events.

cat /proc/acpi/button/lid/LID0/state
state:      open

shut lid

laptop goes to sleep all great.

open lid.  Laptop wakes up, video, wlan0 all comes on line, everything hunky dory - but:

cat /proc/acpi/button/lid/LID0/state
state:      closed

The lid is open, of course!

OK, shut lid.  LCD backlight goes off (so something knows the lid is shut), but no sleep event.  Open lid after a few seconds (maybe 10), and screen lights up and then laptop goes to sleep!

Shut lid (wait for a few seconds), open lid, laptop wakes up fine again, and now:

cat /proc/acpi/button/lid/LID0/state
state:      open

!

So it appears that closing lid flags 'closed' state but opening it doesn't flag 'open' state... unless I then close it again and open which then flags 'closed' state when open so goes to sleep.  So no open it again, and 'state now reports 'open' again.  At this point, back to square one (confused?  I am!).

Using Fn [sleep] in any mode above works OK.  The same happens in X using xfce4 PM or similar.

What is confusing me is that something can see the lid flapping as backlight works on lid open/close.

acpi_listen reports the events as described above, but I can't work out how to record the events when a sleep :)

And ideas/help etc. appreciated, and also I am in the position to be able to debug (with help, of course)!

Thanks,

Nick
-- 
http://linicks.net/

Re: Samsung N145 Plus lid state issue on sleep

[Nick Warne]

On Thu, Sep 26, 2013 at 06:25:00PM +0100, Nick Warne wrote:
> Hi all,
> 
> I have a strange problem, which has been on going on for ages, and I finally decided to look at it (as it is a pain in the arse).
> 
> Brief details:
> 
> Samsung N145 Plus running Slack 14 with handbuilt kernel
> Kernel: Linux 3.11.1 #3 SMP Mon Sep 23 19:09:00 BST 2013 i686 Intel(R) Atom(TM) CPU N455   @ 1.66GHz GenuineIntel GNU/Linux
> I have no modules built in (.config on request if it helps).
> 
> This issue also happened with 'distro' kernel builds... so either it is BIOS issue or hardware fault.  But just in case:
> 
> Boot laptop into console - no X - so running pure acpi events.
> 
> cat /proc/acpi/button/lid/LID0/state
> state:      open
> 
> shut lid
> 
> laptop goes to sleep all great.
> 
> open lid.  Laptop wakes up, video, wlan0 all comes on line, everything hunky dory - but:
> 
> cat /proc/acpi/button/lid/LID0/state
> state:      closed
> 
> The lid is open, of course!
> 
> OK, shut lid.  LCD backlight goes off (so something knows the lid is shut), but no sleep event.  Open lid after a few seconds (maybe 10), and screen lights up and then laptop goes to sleep!
> 
> Shut lid (wait for a few seconds), open lid, laptop wakes up fine again, and now:
> 
> cat /proc/acpi/button/lid/LID0/state
> state:      open
> 
> !
> 
> So it appears that closing lid flags 'closed' state but opening it doesn't flag 'open' state... unless I then close it again and open which then flags 'closed' state when open so goes to sleep.  So no open it again, and 'state now reports 'open' again.  At this point, back to square one (confused?  I am!).
> 
> Using Fn [sleep] in any mode above works OK.  The same happens in X using xfce4 PM or similar.
> 
> What is confusing me is that something can see the lid flapping as backlight works on lid open/close.
> 
> acpi_listen reports the events as described above, but I can't work out how to record the events when a sleep :)
> 
> And ideas/help etc. appreciated, and also I am in the position to be able to debug (with help, of course)!

OK, doing a lot of research, it appears the dsdt is well fubarred.

I have now managed to get a clean build of the extracted dsdt, and testing with various (LIDS) stuff in the code it seems that something is drastically wrong.

Anyhow, I have now got a decent working dsdt that at least sleeps everytime on lid close - although it then goes to sleep again after lid is open, but I can handle that (reverse of my original problem, almost, but at least lid close makes it sleep 100%).

Sleep button (Fn Esc) works as it should.

Anybody good at asl coding?  There is some thing obvioulsy wrong with the logic in this code.

Nick
-- 
FSF Associate Member 5508
http://linicks.net/

Re: Samsung N145 Plus lid state issue on sleep

[Nick Warne]

On Sat, Sep 28, 2013 at 10:14:26PM +0100, Nick Warne wrote:
> On Thu, Sep 26, 2013 at 06:25:00PM +0100, Nick Warne wrote:
> > Hi all,
> > 
> > I have a strange problem, which has been on going on for ages, and I finally decided to look at it (as it is a pain in the arse).
> > 
> > Brief details:
> > 
> > Samsung N145 Plus running Slack 14 with handbuilt kernel
> > Kernel: Linux 3.11.1 #3 SMP Mon Sep 23 19:09:00 BST 2013 i686 Intel(R) Atom(TM) CPU N455   @ 1.66GHz GenuineIntel GNU/Linux
> > I have no modules built in (.config on request if it helps).
> > 
> > This issue also happened with 'distro' kernel builds... so either it is BIOS issue or hardware fault.  But just in case:
> > 
> > Boot laptop into console - no X - so running pure acpi events.
> > 
> > cat /proc/acpi/button/lid/LID0/state
> > state:      open
> > 
> > shut lid
> > 
> > laptop goes to sleep all great.
> > 
> > open lid.  Laptop wakes up, video, wlan0 all comes on line, everything hunky dory - but:
> > 
> > cat /proc/acpi/button/lid/LID0/state
> > state:      closed
> > 
> > The lid is open, of course!
> > 
> > OK, shut lid.  LCD backlight goes off (so something knows the lid is shut), but no sleep event.  Open lid after a few seconds (maybe 10), and screen lights up and then laptop goes to sleep!
> > 
> > Shut lid (wait for a few seconds), open lid, laptop wakes up fine again, and now:
> > 
> > cat /proc/acpi/button/lid/LID0/state
> > state:      open
> > 
> > !
> > 
> > So it appears that closing lid flags 'closed' state but opening it doesn't flag 'open' state... unless I then close it again and open which then flags 'closed' state when open so goes to sleep.  So no open it again, and 'state now reports 'open' again.  At this point, back to square one (confused?  I am!).
> > 
> > Using Fn [sleep] in any mode above works OK.  The same happens in X using xfce4 PM or similar.
> > 
> > What is confusing me is that something can see the lid flapping as backlight works on lid open/close.
> > 
> > acpi_listen reports the events as described above, but I can't work out how to record the events when a sleep :)
> > 
> > And ideas/help etc. appreciated, and also I am in the position to be able to debug (with help, of course)!
> 
> OK, doing a lot of research, it appears the dsdt is well fubarred.
> 
> I have now managed to get a clean build of the extracted dsdt, and testing with various (LIDS) stuff in the code it seems that something is drastically wrong.
> 
> Anyhow, I have now got a decent working dsdt that at least sleeps everytime on lid close - although it then goes to sleep again after lid is open, but I can handle that (reverse of my original problem, almost, but at least lid close makes it sleep 100%).
> 
> Sleep button (Fn Esc) works as it should.
> 
> Anybody good at asl coding?  There is some thing obvioulsy wrong with the logic in this code.

OK, I have hung myself.

Even finding this bug report, and shipping off a quick mail, deadly, spookily all quiet on the DSDT front.

https://bugzilla.kernel.org/show_bug.cgi?id=17081

So for googlers everywhere, I have at least got a dirty hack:

http://www.linicks.net/dsdt/

It's not right, nor even wrong, but at least it works (sorta).

Nick
-- 
FSF Associate Member 5508
http://linicks.net/

Re: Linux 3.12-rc2

[Nick Warne]

Hi all,

I have couple of  build warnings.  Not sure if this happened with rc1, as I only have moved across to the rc trees:

gcc (GCC) 4.2.4 on amd64 - no modules build:


1)
...
  GEN     lib/crc32table.h
  CC      lib/crc32.o
lib/crc32.c: In function ‘crc32_be’:
lib/crc32.c:263: warning: passing argument 4 of ‘crc32_be_generic’ from incompatible pointer type
lib/crc32.c: In function ‘__crc32c_le’:
lib/crc32.c:199: warning: passing argument 4 of ‘crc32_le_generic’ from incompatible pointer type
lib/crc32.c: In function ‘crc32_le’:
lib/crc32.c:194: warning: passing argument 4 of ‘crc32_le_generic’ from incompatible pointer type
  CC      lib/fonts/fonts.o
...

2)
  CC      lib/radix-tree.o
lib/radix-tree.c: In function ‘radix_tree_next_chunk’:
lib/radix-tree.c:805: warning: comparison is always false due to limited range of data type
  CC      lib/ratelimit.o
...


Nick
-- 
http://linicks.net/