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

0 Members and 9 Guests are viewing this topic.

Offline tangrs

  • LV5 Advanced (Next: 300)
  • *****
  • Posts: 229
  • Rating: +98/-0
    • View Profile
    • tangrs blog
Re: Calling all Linux Kernel developers!
« Reply #420 on: December 01, 2012, 06:47:34 am »
Ah yeah, obviously, thanks :)

And congratz for the touchpad LCD :)
(Also, Clickpad coming soon, as ou said it should actually work ?)

Yeah, Clickpads and Touchpads are pretty much exactly the same (AFAIK). Pretty much the only difference is the keypad.

Offline Vogtinator

  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1193
  • Rating: +108/-5
  • Instruction counter
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #421 on: December 01, 2012, 07:27:23 am »
My friend owns a clickpad cas. Maybe I can persuade him to try it.
I'll try writing support for the adc (battery voltage) today, so we can see the power consumption.

Offline tangrs

  • LV5 Advanced (Next: 300)
  • *****
  • Posts: 229
  • Rating: +98/-0
    • View Profile
    • tangrs blog
Re: Calling all Linux Kernel developers!
« Reply #422 on: December 01, 2012, 07:30:14 am »
My friend owns a clickpad cas. Maybe I can persuade him to try it.

Support for clickpad isn't really ready yet so you can probably hold it off until a bit later.

I'll try writing support for the adc (battery voltage) today, so we can see the power consumption.

Awesome!
« Last Edit: December 01, 2012, 07:31:01 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 #423 on: December 01, 2012, 08:07:23 am »
The struct clcd_panel classic_lcd_panel uses values < 6 for margin's and hsync_len too, so clcdfb_check will return -EINVAL.
Could you test whether X and directfb work on touch- and clickpads?

Edit: I just wrote the driver for the adc, but reads from 0xC4000000 - 0xC40001DF (mapped to 0xfed7ee21 - 0xfed7f000) always return 0.
Frustrated I began to write a driver for the LEDs (in AHB region), but they're always off, even if I turn them on manually.
# echo 1 > /proc/red_led
Red LED turned ON
# cat /proc/red_led
Red LED is OFF
Same for green LEDs.
Could the problems be related?

Edit 2: Everytime reads from the led control register return 0x1643 (0b01011001000011: Green blink data, green iteration, red blink data, red iteration).
I think writes are just ignored.
Could the cause be
Quote
900B0018 (R/W): Disable bus access to peripherals. Reads will just return the last word read from anywhere in the address range, and writes will be ignored.
?
« Last Edit: December 01, 2012, 11:41:00 am by Vogtinator »

Offline compu

  • LV5 Advanced (Next: 300)
  • *****
  • Posts: 275
  • Rating: +63/-3
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #424 on: December 01, 2012, 11:50:02 am »
I think the LED has a Lock register similar to the watchdog.
The OS seems to write 0x1ACCE551 to 0x90110C00 before accessing LED registers, but I've tried that and it doesn't work.

Offline Vogtinator

  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1193
  • Rating: +108/-5
  • Instruction counter
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #425 on: December 01, 2012, 11:55:06 am »
ACCE55? Very funny, TI..
I just found a way how to turn the device into standby:
Code: [Select]
writel(~0, NSPIRE_APB_VIRTIO(NSPIRE_APB_POWER + 0x18));Display is off, only reset turns on (and resets). ;-)

Offline Adriweb

  • Editor
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1708
  • Rating: +229/-17
    • View Profile
    • TI-Planet.org
Re: Calling all Linux Kernel developers!
« Reply #426 on: December 01, 2012, 11:58:07 am »
ACCE55? Very funny, TI..

That's just awesome x)

And what you did too :)
My calculator programs
TI-Planet.org co-admin.
TI-Nspire Lua programming : Tutorials  |  API Documentation

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 #427 on: December 01, 2012, 12:03:32 pm »
Disabling bus access to all bus peripherals ? Bad.
Fiddling with the LED ? Good.
« Last Edit: December 01, 2012, 12:04:22 pm 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 #428 on: December 01, 2012, 12:06:58 pm »
Not if you want to do it :P

Offline InspiredByCas

  • LV3 Member (Next: 100)
  • ***
  • Posts: 44
  • Rating: +4/-1
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #429 on: December 01, 2012, 02:00:57 pm »
Try starting linucx in Press-to-test Mode. If you put the linuxloader (or the script) in the ndless startup folder, it should be executed, even in Press-to-test Mode. I am not sure if it works with linuxloader, but other things in ndless startup folder are executed in Press-to-test Mode.
The reason why I write this, is that Norse (the cool app for morsing around with the LED, not compiled for 3.1) worked sometimes when started i Press-to-test Mode, as I read somewhere.

You can exit Press-to-test Mode anytime by sending a complete EMPTY file with the file name 'Exit Test Mode.tns' (just create a empty text file and rename it, but watch out, it's case-sensitive!) to the - regulary only and empty - folder in the CAS.
To start this Mode, just hold Esc+On when calc is off.
Then try your LED code again and try reading if the values in the memory are different from normal mode (they should be, even before writing new values), because the LED blinks in Press-to-test mode.

Also cool news with the power management :)

Offline Vogtinator

  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1193
  • Rating: +108/-5
  • Instruction counter
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #430 on: December 01, 2012, 02:33:59 pm »
Quote
Try starting linucx in Press-to-test Mode. If you put the linuxloader (or the script) in the ndless startup folder, it should be executed, even in Press-to-test Mode. I am not sure if it works with linuxloader, but other things in ndless startup folder are executed in Press-to-test Mode.
The reason why I write this, is that Norse (the cool app for morsing around with the LED, not compiled for 3.1) worked sometimes when started i Press-to-test Mode, as I read somewhere.
Yes, I knew already (guess why ;-) )

Quote
You can exit Press-to-test Mode anytime by sending a complete EMPTY file with the file name 'Exit Test Mode.tns' (just create a empty text file and rename it, but watch out, it's case-sensitive!) to the - regulary only and empty - folder in the CAS.
To start this Mode, just hold Esc+On when calc is off.
I had to do this once already, because I thought, "Press-to-test" is like a lcd- and keypad test mode.
I was like "F**k, how can I get out from here!?".

Quote
Then try your LED code again and try reading if the values in the memory are different from normal mode (they should be, even before writing new values), because the LED blinks in Press-to-test mode.
I'll try that.

Quote
Also cool news with the power management
I'd rather call that stupidity ;-)

Edit: Nope, linuxloader can't find the kernel image. At least not if I load it with "kernel linux/zImage.tns", maybe the path is different.
« Last Edit: December 01, 2012, 02:51:36 pm by Vogtinator »

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 #431 on: December 01, 2012, 02:54:29 pm »
The path is indeed slightly different, but I don't remember exactly what it is. The PTT-related code is quite early (low addresses) in the memory image of the OS; also, RootDoc and the PTTKiller programs may help :)
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 #432 on: December 01, 2012, 02:57:14 pm »
Ok, I'll try that, too.
But for now, I did it and GPIOs are working :D
At least GPIO 8 is low the whole time and GPIO 1 high.
Touchpad, we are coming to you  :devil:

Edit: With rootDoc it only displays "Documents (empty folder)" in press-to-test mode..
Edit 2: HELP! I can't get out of Press-to-test anymore :-( Holding ESC at startup doesn't work at all and rootdoc seems to block "Exit Test Mode.tns"
Edit 3: I tried esc twice and after that it wouldn't boot at all :-( I had to take out the battery.. But now I can send the linux kernel to "/exammode/usr/zImage.tns".
« Last Edit: December 01, 2012, 03:28:21 pm by Vogtinator »

Offline compu

  • LV5 Advanced (Next: 300)
  • *****
  • Posts: 275
  • Rating: +63/-3
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #433 on: December 01, 2012, 03:31:24 pm »
AFAIK, USB file transfers aren't working anymore after using RootDoc (I think I read that somewhere) ;D

But you can reboot and hold ESC so that RootDoc isn't launched and then transfer the exit PTT file.

Edit: Nope, linuxloader can't find the kernel image. At least not if I load it with "kernel linux/zImage.tns", maybe the path is different.
Try /documents/linux/zImage.tns instead (I guess linuxloader2 searches in the current directory, which is /exammode/usr while in PTT mode instead of /documents)

btw, I'm pretty sure that you can't change the LED in PTT either, I've done some tests a while ago :P

EDIT: Oh well, you ninja'd me with your edit :D
« Last Edit: December 01, 2012, 03:32:49 pm by compu »

Offline Vogtinator

  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1193
  • Rating: +108/-5
  • Instruction counter
    • View Profile
Re: Calling all Linux Kernel developers!
« Reply #434 on: December 01, 2012, 03:42:29 pm »
FFFFFFFFFFFFUUUUUUU
I WANT TO GET OUT OF THIS HELL
BTW: No, the led's don't work, still 0x1643 (what seems absolutely right)

Edit: Maintenance Menu and cleared /documents.. I hope it boots again..
Edit2: Nope, reboot loop because of ndless_resources.tns missing..
Edit3: Reinstalling OS now..
Edit4: Didn't work, hangs at clock screen, doing complete reformat.
Edit5: Diagnostics menu -> ADC Test displays following:
ADC0: LBAT 4,07 V
ADC1: VBATT 0V <-WTF The wiki is wrong here
ADC2: VSYS 4.01V
ADC3: KBID 0.2V
ADC4: B12 0.3V
ADC5: VBUS 0.006V
ADC6: VSLED 0.09V

Edit6: YEAH Finally I'm out! Now I can test I²C!
Edit9001: Tangrs linuxloader from github doesn't work.. Only few colored pixels on top of the screen
Edit9002: Which frequency is correct for the touchpad?
« Last Edit: December 01, 2012, 05:14:18 pm by Vogtinator »