Author Topic: Calling all Linux Kernel developers!  (Read 348111 times)

0 Members and 3 Guests are viewing this topic.

Offline Vogtinator

  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1193
  • Rating: +108/-5
  • Instruction counter
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #570 on: January 12, 2013, 07:12:32 pm »
My current build is deleted, I'm currently removing dirty lines.

But if you really want to get it now, compile it yourself:
https://github.com/Vogtinator/linux/tree/testing

Edit: Kernel is attached.
But I still have to edit drivers/i2c/busses/i2c-designware-core.c.

Edit2: I compiled psplash and now we have a nice progress bar on boot:
« Last Edit: January 13, 2013, 01:13:15 pm by Vogtinator »

Offline tangrs

  • LV5 Advanced (Next: 300)
  • *****
  • Posts: 229
  • Rating: +98/-0
    • View Profile
    • tangrs blog
Re: Calling all Linux Kernel developers!
« Reply #571 on: January 14, 2013, 05:08:29 am »
Edit2: I compiled psplash and now we have a nice progress bar on boot:


Very nice!

Edit: Added a backlight driver for Nspire Linux so the backlight also turns off as the LCD powers off. That should save some power and not show the ugly white fading screen when the LCD turns off.

I am also planning to get a contrast driver working for the classics so we can remove the ugly /proc/contrast and /proc/backlight files.
« Last Edit: January 14, 2013, 07:19:58 am by tangrs »

Offline Vogtinator

  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1193
  • Rating: +108/-5
  • Instruction counter
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #572 on: January 14, 2013, 08:20:12 am »
Quote
I am also planning to get a contrast driver working for the classics so we can remove the ugly /proc/contrast and /proc/backlight files.
/sys/class/backlight interface?
That'd be great!

I wonder where the right place for /proc/adc is..

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: Calling all Linux Kernel developers!
« Reply #573 on: January 14, 2013, 09:32:17 am »
Quote
I am also planning to get a contrast driver working for the classics so we can remove the ugly /proc/contrast and /proc/backlight files.
Sure, would be good :)

Quote
I wonder where the right place for /proc/adc is.
I think it's something more complicated involving the battery and/or power stuff. Not necessarily a must for the very first mainline RFC submission.
« Last Edit: January 14, 2013, 09:34:08 am by Lionel Debroux »
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline Vogtinator

  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1193
  • Rating: +108/-5
  • Instruction counter
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #574 on: January 14, 2013, 09:44:52 am »
Quote
I think it's something more complicated involving the battery and/or power stuff.
I think http://www.mjmwired.net/kernel/Documentation/hwmon/sysfs-interface is right, but no documentation :-(
Hopefully there's a simple driver already..

Quote
Not necessarily a must for the very first mainline RFC submission.
Not really necessary, but so we know whether the battery is charging.
Maybe there's a small x app which displays the charge level or at least the voltages.

Offline tangrs

  • LV5 Advanced (Next: 300)
  • *****
  • Posts: 229
  • Rating: +98/-0
    • View Profile
    • tangrs blog
Re: Calling all Linux Kernel developers!
« Reply #575 on: January 19, 2013, 05:12:56 am »
Hmmm, I'm starting to implement a CPU frequency scaling driver. At the moment, it simply reports the CPU frequency.

Now, I need some help with frequency scaling. If we assume that the base speed won't change, what would be a good way to determine a table of "safe" speeds to scale to? Should we be touching the base speed? What happens if the user overclocks the calculator? How do we ensure that AHB/CPU speeds are always within safe limits?

Any ideas?

Edit: I'll try a list of "safe" divisors for now.
« Last Edit: January 19, 2013, 05:19:32 am by tangrs »

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: Calling all Linux Kernel developers!
« Reply #576 on: January 19, 2013, 05:23:47 am »
The experience with the CX shows that on the CX, IMO, the AHB frequency should never be touched. The default is 66 MHz, and NAND memory corruption occurs quickly if the AHB is set to 75 MHz. 72 MHz seems to be safer, but then it's less than 10% overclocking margin.
The Clickpad & Touchpad have higher tolerance to AHB overclocking, IIRC.
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline tangrs

  • LV5 Advanced (Next: 300)
  • *****
  • Posts: 229
  • Rating: +98/-0
    • View Profile
    • tangrs blog
Re: Calling all Linux Kernel developers!
« Reply #577 on: January 19, 2013, 05:25:01 am »
The experience with the CX shows that on the CX, IMO, the AHB frequency should never be touched. The default is 66 MHz, and NAND memory corruption occurs quickly if the AHB is set to 75 MHz. 72 MHz seems to be safer, but then it's less than 10% overclocking margin.
The Clickpad & Touchpad have higher tolerance to AHB overclocking, IIRC.

It's okay if the AHB speed is slower than 66MHz right? I'm working with the values that Nover gives me and avoiding everything that's "dangerous".

Offline ElementCoder

  • LV7 Elite (Next: 700)
  • *******
  • Posts: 611
  • Rating: +42/-2
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #578 on: January 19, 2013, 05:44:04 am »
A bit slower wouldn't hurt I think, though high values indeed corrupt your NAND quickly. IIRC, the warnings on the CPU could be ignored it was only the AHB warning that should be taken serious.

Some people need a high five in the face... with a chair.
~EC

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: Calling all Linux Kernel developers!
« Reply #579 on: January 19, 2013, 05:49:22 am »
The CPU warning had better not be ignored, otherwise the calculator will just crash ;)
The problem is, a wide range of maximum tolerated CPU clock speeds have been reported. Few CX calculators can run in a stable manner above 252 MHz, but some have been reported to crash at 222 MHz - so you probably shouldn't let the driver go over 210 or 216 MHz. For the first mainline submission, and even later IMO, stability trumps squeezing the last bit of performance :)
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline willrandship

  • Omnimagus of the Multi-Base.
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2953
  • Rating: +98/-13
  • Insert sugar to begin programming subroutine.
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #580 on: January 19, 2013, 05:53:33 am »
Why build in such a limitation? just make sure there's a warning somewhere, and make the default lower. Ideally, the default would be normal, so new users can't blame their problems on it.

Offline tangrs

  • LV5 Advanced (Next: 300)
  • *****
  • Posts: 229
  • Rating: +98/-0
    • View Profile
    • tangrs blog
Re: Calling all Linux Kernel developers!
« Reply #581 on: January 19, 2013, 05:57:31 am »
Why build in such a limitation? just make sure there's a warning somewhere, and make the default lower. Ideally, the default would be normal, so new users can't blame their problems on it.

Sounds good. I'll only include frequencies that Nover doesn't report as dangerous.

Edit: Implemented a simple cpufreq driver. It can only scale between two frequencies though: half of base freq and 1/4 of base freq. It's limited because we can't touch the AHB speed (or else, drivers relying on the AHB and APB clocks will be all messed up) unless we notify the drivers of the change. I'm still looking into it.
« Last Edit: January 19, 2013, 09:39:48 pm by tangrs »

Offline Levak

  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1002
  • Rating: +208/-39
    • View Profile
    • My website
Re: Calling all Linux Kernel developers!
« Reply #582 on: January 22, 2013, 03:14:13 pm »
I suppose that this can't be solved ? (my stuff is absolutly not up to date, if it is the problem)
Don't bother on the yyyyyyyyyyyyyyyy... stuff, I know it has been solved.
« Last Edit: January 22, 2013, 03:16:32 pm by Levak »
I do not get mad at people, I just want them to learn the way I learnt.
My website - TI-Planet - iNspired-Lua

Offline Vogtinator

  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1193
  • Rating: +108/-5
  • Instruction counter
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #583 on: January 22, 2013, 03:25:56 pm »
It's your script, theres "#boot" instead of "boot" which gives an "Unknown command" error.

Edit: "Ramdisk too large" Oops, my mistake  :-[ Use the initrd from tangrs for now
« Last Edit: January 22, 2013, 03:32:54 pm by Vogtinator »

Offline Hooloovoo

  • LV5 Advanced (Next: 300)
  • *****
  • Posts: 225
  • Rating: +22/-0
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #584 on: January 22, 2013, 06:01:13 pm »
Is it possible to get X working on a click pad/touchpad? Mine complains about the color depth being unsupported. Is there a way around that?
"My world is Black & White. But if I blink fast enough, I see it in Grayscale." -tr1p1ea
Spoiler For some of the calcs I own:



(actually I have quite a few more than this, but I don't feel like making bars for them all.)