yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] tomj333:
so has anyone got this to work on the HD withought it hanging?
[Touch HD Windows Mobile ROM Development] abats:
The testfiles are in the first post Bro.
[Touch HD Windows Mobile ROM Development] jim256:
...does no one else think that this looks kind of useful?

xmoo...maybe you could pass this on to your mystery other HD dev

Have a look

http://xdaforums.com/showpost.php?p=3235256&postcount=2873
[Touch HD Windows Mobile ROM Development] orux:
Well; I've found a way to send framebuffer to the screen, as you can see below (sorry about the bad quality of picture).

First note: It,s a "primitive" way; like spl does. It is a heavy routine and the frame per second are very bad. It would be difficult that supports android.

2ºStill problems: colour, right displacement, hangs after a time.

But it's fun, and I know now more about mddi interface :)

This weekend I'll document it in the blackstone wiki, if i have enought time.
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
Ask yourself this question, do we want to display more colors?

More colors requires more bandwidth and more power to do the processing.

The graphics speed problems we have with the HD compared to lower res devices has already been shown to be due to the HD having a higher resolution schreen requiring alot more bandwidth and power from the graphics chip.

Asking even more from it in terms of processing a multitude more colors will make the graphics and device even slower. Not only will it be even slower but battery life will go down too.

Lets just focus on getting Linux and android to work before going that route.
[Touch HD Windows Mobile ROM Development] orux:
I dont know what happens with colours; but spl sends pixels to the screen in rgb666 format, instead of rgb565 (like wince does).

Blackstone has got 20% pixels more than 640x480 devices, it needs draw each time more framebuffer. Then the framebuffer is sent to the display througth dma interface.

Next step is know how wince uses mdp-dma interface to send framebuffer to display. But i havent found (yet) in wince the routines that does this work.
[Touch HD Windows Mobile ROM Development] BigDaemon:
Yeah guy, this looks like a big step in the right direction and i guess it brings us a very big step nearer to boot Android on our Blackstones.

Nice work!!
[Touch HD Windows Mobile ROM Development] patp:
Well done Orux!!!

This is great, because with a working console people can do more active debugging on the device. This is the breakthrough point for linux on the HD.
[Touch HD Windows Mobile ROM Development] brumbrum:
Nice work! :-)

Isn't the "graphical mode" in android also using framebuffer, just like the console? If so: Is it possible to start debug real functions in the android-system on the HTC HD now? That would be really cool if it was possible to start getting the radio and applications to work. Or does the radio already work since it is the same as in G1?

Anybody that know exacly what differ the components in G1 and HD? Would be nice with a list of components so we could focus on getting a working system to run.

I really look forward to when it is possible to flash the device with Android instead of Windows! :-) I wonder how far into the future this is...
[Touch HD Windows Mobile ROM Development] orux:
We have a ssh console running with Angstrom dist, see: http://wiki.xda-developers.com/index.php?pagename=BlackstoneLinux

Blackstone has a lot in common with Raph and Diamond, so it's probably that all that works on them, works on blackstone: http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux

I have improve a bit fps, but still "freezes" at the end; mddi module is complex.
[Touch HD Windows Mobile ROM Development] BigDaemon:
Not so fast brumbrum, if i understand it right, what orux is doing right now is just a workaround, but not a final solution for the screen-problem, isn´t it??

We stil have to fix the problem with a final solution before starting to get the Functions of Android running....

Please correct me if i am wrong :-)
[Touch HD Windows Mobile ROM Development] NeoS:
As far as i can see, this enables more and specific development on Android on the blackstone. You now can actually SEE what your typing. ;)
[Touch HD Windows Mobile ROM Development] abeery:
Excellent work guys and gals... being able to see what you're doing even if slow is a hugh step forward and should potentially open the floodgates for developers... a reluctance to work blind has kept me away but even I'm willing to wade into these waters now!

Blessings one and all!
[Touch HD Windows Mobile ROM Development] p3ngwin:
HOLY CRAP!

another major milestone achieved, WELL DONE ORUX !
[Touch HD Windows Mobile ROM Development] JohnQ:
tip: use resco explorer to delete the zImage.txt's suffex .txt

btw, do i have to wait 10 more min for the booting? it hangs on Haret: Botting Linux....
[Touch HD Windows Mobile ROM Development] gerdgerdgerd:
i have wait about 20 min for the booting ... and its still hanging: Bootin Linux....
[Touch HD Windows Mobile ROM Development] nicolecoco03:
Same problem for me :/
[Touch HD Windows Mobile ROM Development] ddhb:
Maybe the Android Version of the G1 is working on our Blackstone?
[Touch HD Windows Mobile ROM Development] stefh:
Ok I am new here and actually I will let my buying decision of the Touch HD depend on being able to run Android...

What I find so strange is that one would think Android could be ported directly, because of the same hardware as G1, except for the bigger screen, the absence of a keyboard and a better camera.

When I look at detailed specs of both phones on http://pdadb.net/index.php?m=pdacomparer (you have to select both phones first) I notice all the same stuff being used in both phones.

CPU:

32 bit Qualcomm MSM7201A @ 528 MHz

ARM1136EJ-S with ARMv6 instruction set

Bigger ROM and RAM capacity on Touch HD.

Same display specs apart from the resolution. But Actually I wouldn't care of Android runs on a lower resolution.

Same audio chip.

Same phone controller Qualcomm MSM7201A (QDSP4000, QDSP5000)

Same GPS chipset Qualcomm MSM7201A gpsOne.

But I don't know **** about programming, but one would say it should not be too difficult to port.

I depend on you guys! Thanks a lot for all the effort so far!

Regards from the Netherlands
[Touch HD Windows Mobile ROM Development] orux:
Well; i've done some progress: http://imagebin.org/37232

It reaches the end, and opens ok a ssh console, BUT:

-sometimes the screen shut down suddenly :(

-because it is a heavy routine, i've to use a trick; only sending 1 from each 5 frames it works fine.

Now the driver draws all the screen each time. I am going to work about that only the lines that needs be paint will be send to the screen.

I INSIST; this is not probably the correct way to see android running blackstone. We need to learn how to send the framebuffer without conversions between rgb565 and rgb666, through dma path.

The problem is that MDDI interface is very complex, and there is not documentation about it.
[Touch HD Windows Mobile ROM Development] dwaradzyn:
Nice work orux. Would you mind posting some zImage/changed files/diffs for others to play with it?
[Touch HD Windows Mobile ROM Development] orux:
Tomorrow I am going to let my pda have a rest, after thousands of soft-resets. I'll document all my work and post it.

The problem with a diff is that I'm playing with a very dirty and old (december) snapshot of linuxtogo kernel (htc-msm-2.6.25).

I'm working with the diff made by pichurri ( http://www.gavero.com/pichurri/blackstone/kernel-2008-12-28.diff ) one month ago.

If someone has got this kernel (htc-msm-2.6.25) updated with pichurri's work, it would be nice that he post a diff.
[Touch HD Windows Mobile ROM Development] orux:
This is a new diff that updates kernel-2008-12-28.diff posted in wiki: http://wiki.xda-developers.com/index.php?pagename=BlackstoneLinux

It can be applied to a recent kernel dowloaded from linuxtogo git. All the necessary is in the wiki (you need to replace kernel-2008-12-28.diff by black-orux-020209.diff).

It works, with weird display. It's a good start point.

I recommend use it with angstrom initrd; it has no sense tray to run android over it yet.

I'll do another diff when I probe the "other display way" with this kernel.
[Touch HD Windows Mobile ROM Development] xmoo:
3 More Exams left.

Nice job ornux!
[Touch HD Windows Mobile ROM Development] Rayzer HD:
thanks orux :)

but i have a problem with patching with your diff there are some errors. it says 4 of 5 was failured and then in the last step by make for creating the zimage there is at the end no zimage in boot directory :(

what can i do? now i will delete all files and try it again with the old diff...

edit: orux did u take some other files as in the wiki are called?i mean exept your diff :)

edit2: sry i cant do it :( can u upload your zimage plz? i did exactly what is written in wiki but there are only errors... and no zimage...

MfG Rayzer HD
[Touch HD Windows Mobile ROM Development] orux:
It is a strange thing, because I download a entire kernel from git, and probe the diff before post it.

Did you do the change of branch before patch? (git checkout -b htc-msm-2.6.25 origin/htc-msm-2.6.25)

Can you post the patch failures?

It has no sense tray to compile if you do not resolve patch conflicts.
[Touch HD Windows Mobile ROM Development] brumbrum:
Is it possible to put the complete source, patched and ready, for download?

Also, is it possible to create a complete package with all img-files and zImage compiled for download?

How much does the kernel diff from the kernel used in G1?

How much does the system.img and other filesystem-files diff from the G1?
[Touch HD Windows Mobile ROM Development] patp:
Orux, does this diff compile with 2.6.25 or 2.6.27?
[Touch HD Windows Mobile ROM Development] orux:
I'm using htc-msm-2.6.25 branch still. Porting to 2.6.27 (Raphael and Diamond) is recent (one or two weeks) and I'm not sure if it's stable enough for Blackstone.

I'd rather wait a bit, and try to solve this problem with 2.6.25 kernel, which I know better.
[Touch HD Windows Mobile ROM Development] ddhb:
I'm not so good in english and i can't follow your posts really good. So i have one question:

Is the screen issue eliminated?
[Touch HD Windows Mobile ROM Development] Rayzer HD:
Huhu good morning everybody! :D

So i did try it again an i will now post all the steps:

git clone git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git

remote: Counting objects: 1182075, done.

remote: Compressing objects: 100% (219833/219833), done.

Indexing 1182075 objects.

100% (1182075/1182075) done

remote: Total 1182075 (delta 978668), reused 1160213 (delta 957103)

Resolving 978668 deltas.

100% (978668/978668) done

Checking files out...

100% (24269/24269) done

git checkout -b htc-msm-2.6.25 origin/htc-msm-2.6.25

git checkout: branch htc-msm-2.6.25 already exists

wget http://www.codesourcery.com/gnu_too...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 -O arm-2008q1-126-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2

tar -xjf arm-2008q1-126-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2

now i did copy your diff in kernel dir

patch -p1 < black-orux-020209.diff

patching file arch/arm/configs/htcblackstone_defconfig

patching file arch/arm/mach-msm/Kconfig

Hunk #1 FAILED at 46.

1 out of 1 hunk FAILED -- saving rejects to file arch/arm/mach-msm/Kconfig.rej

patching file arch/arm/mach-msm/Makefile

Hunk #1 FAILED at 10.

1 out of 1 hunk FAILED -- saving rejects to file arch/arm/mach-msm/Makefile.rej

patching file arch/arm/mach-msm/board-htcblackstone.c

can't find file to patch at input line 1581

Perhaps you used the wrong -p or --strip option?

The text leading up to this was:

--------------------------

|diff --git a/arch/arm/mach-msm/htc_fb_console.c b/arch/arm/mach-msm/htc_fb_console.c

|index faa3a49..b9475e3 100644

|--- a/arch/arm/mach-msm/htc_fb_console.c

|+++ b/arch/arm/mach-msm/htc_fb_console.c

--------------------------

File to patch:

ok now there are the first erros...

yesterday i did insert after this "File to patch:" black-orux-020209.diff and click on Enter but it did comes again and again and i did again and again and then it maybe finished and then im already in the shell...

ok but now i did it only one time and my pc is in this state like u see above i could insert your diff again... :D

ok whats going on and what can i do now? i will let them in this state until u answerd my orux :)

a notice at the end i did this all on a remote server with putty^^

MfG Rayzer HD
[Touch HD Windows Mobile ROM Development] orux:
MfG Rayzer HD:

I'm working now; I can't help you now. I'll help you when arrive at my home.

ddhb:

Sorry, the problem is my bad english, not yours.

Screen does not work. Still problems.
[Touch HD Windows Mobile ROM Development] Rayzer HD:
Ok i will still waiting :D

And a question: is it right first to patch and then make the config(make htcblackstone_defconfig ARCH=arm) like it is said in the wiki?

MfG Rayzer HD
[Touch HD Windows Mobile ROM Development] pichurri:
Hey Orux!

First, congrats!!! great job!!! :)!!

So, I went through the patch, but I didn't see any changes in the mddi/mdp, msm_fb.c or htc_fb_console.c...could you check that you uploaded the right patch, :p, plz?

:)
[Touch HD Windows Mobile ROM Development] orux:
Rayzer HD;

git checkout -b htc-msm-2.6.25 origin/htc-msm-2.6.25

git checkout: branch htc-msm-2.6.25 already exists

I think this is not correct.

After git clone, you will be in *master branch; my log:

jose@jose-desktop:~/blackstone2/kernel4/kernel$ git checkout -b htc-msm-2.6.25 origin/htc-msm-2.6.25

Checking out files: 100% (8964/8964), done.

Branch htc-msm-2.6.25 set up to track remote branch refs/remotes/origin/htc-msm-2.6.25.

Switched to a new branch "htc-msm-2.6.25"

I do not know why your are in htc-msm-2.6.25 branch after git clone.

did you do git clone ...... in a clean directory?

I've replayed the patch, and works fine in my computer; my log:

jose@jose-desktop:~/blackstone2/kernel4/kernel$ patch -p1 < black-orux-020209.diff

patching file arch/arm/configs/htcblackstone_defconfig

patching file arch/arm/mach-msm/Kconfig

patching file arch/arm/mach-msm/Makefile

patching file arch/arm/mach-msm/board-htcblackstone.c

patching file arch/arm/mach-msm/htc_fb_console.c

patching file arch/arm/mach-msm/irq.c

patching file arch/arm/tools/mach-types

patching file drivers/input/touchscreen/msm_ts.c

patching file drivers/video/msm/mddi_client_toshiba.c

patching file drivers/video/msm/mdp.c

jose@jose-desktop:~/blackstone2/kernel4/kernel$

Pichurri; how long time!!!!

This is a diff done with an update (yesterday) git clone htc-msm-2.6.25, plus your initial patch (conflicts resolved) plus minor changes.

It is a new start point, with the latest updates in htc-msm-2.6.25 branch.

Now I'm going to do another diff with the new method that I've found to send the fb to the display. This is a "very experimental" way, and I think it's better the initial diff as "start point".

Can you probe the black-orux-020209.diff ??
[Touch HD Windows Mobile ROM Development] orux:
Rayzer HD;

Hmmm; I think that the answer is yes; but delete all, included hidden files and folders (.git and others) ??
[Touch HD Windows Mobile ROM Development] Rayzer HD:
yes also the files i get per git clone... i can do again but this would be the third time...^^

ok will do it again... and this is also your source: git clone git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git yeah?

Rayzer HD
[Touch HD Windows Mobile ROM Development] orux:
jose@jose-desktop:~/blackstone2/kernel$ git clone git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git
[Touch HD Windows Mobile ROM Development] pichurri:
Hey there, yup, long time no see! :)!

Ahhh, now I understand, black-orux-020209.diff is a patch against the latest git repository of 2.6.25 diamond/ralph, to take that as a starting point, but it does not contain anything for the new method to write to the screen...(I think everybody was expecting a patch for that thou, :p).

Now I'm dying to see my blackstone to output something legible....:P, could you post/send the patch that contains the "not so correct" fix of screen output...plz

Again, great job!
[Touch HD Windows Mobile ROM Development] orux:
Well,

Pichurri, for you:

Using "Running Angstrom" instructions from wiki:

Angstrom's initrd -->downloaded from wiki

default.txt, haret.exe, zImage --> below attached zip

Connect the phone to your PC using the USB cable (actyvesync mode)

(15-20 seconds before first screen displayed)

calibrate, and, (if it works) fun!!

probed 4 times, 3 OK; 1 KO (no boot)

Warning: Please note this is still in very early stages. If you don't know what you are doing...YOU WILL BRICK YOUR PHONE, we take no responsability. You've been warned.
[Touch HD Windows Mobile ROM Development] patp:
just out of interest orux, what happens if you run Android with this kludged screen routine?
[Touch HD Windows Mobile ROM Development] orux:
I have not try it. First we need that linux runs correctly.

Android, X, ... would be next step.
[Touch HD Windows Mobile ROM Development] Rayzer HD:
thanks orux :)

i tried with android hangs up after haret loading 100% i will try some other configurations we will see, but "First we need that linux runs correctly.

Android, X, ... would be next step. " -> Thats right! :)

Rayzer HD
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
I'm reflashing my phone with the latest Duty rom to see if I can run it then.

With my current rom it won't run at all.
[Touch HD Windows Mobile ROM Development] pichurri:
!!! :) ! nice. It booted!

During the day I'll check the previous patch you sent and I'll put it on the wiki.

Ps: could you send me a diff of what you did to get the screen working, I really want to have a look at it.
[Touch HD Windows Mobile ROM Development] orux:
I have the code ready. I'll make a diff this evening, at home.
[Touch HD Windows Mobile ROM Development] body85:
I´ve a Questin:

G1 and HD are the same Hardware right?

It isnt possilbe to make a dump of the G1 and flash it over the HD?

With bootloader, software drivers....??

i think the people here have 2 Answers....

1. Oh **** why we dont think this??

2. Shut up :-P
[Touch HD Windows Mobile ROM Development] BigDaemon:
Because the Hardware is NOT exactly the same!

Chipset/CPU is the same, but: RAM is different (not only in size i guess), DISPLAY is different (which looks like being the main-problem at the moment)

It is NEARLY the same, but only nearly.

If the guys here could fix the screen-problem this idea MIGHT work with some little modification on the G1-Rom, but not now as we haven´t solved this screen-problem
[Touch HD Windows Mobile ROM Development] body85:
why we dont ask HTC for a driver :-P

"DISPLAY is different (which looks like being the main-problem at the moment)"

but its worked on a TyTN 2 and others.... they have a different display too or?
[Touch HD Windows Mobile ROM Development] jim256:
Lol o gosh HTC would NEVER even bother responding to that message let alone write / buy a driver and give it away to us.

As for TyTN 2 and others...I'm willing to bet they had heavy modifications, no one just slapped a G1 rom on a TyTN 2 and it worked w/o any configuration / patches / rewriting of drivers etc etc...

Is the Vogue included in "...and others..." ? Having android on the vogue had nothing to do w/ getting anything from the G1, dzo / martin just got it all going himself well before the G1 was even released. And even now after it's been released I'm pretty sure he's taken nothing from it's ROM.

@Devs...

Please keep it up I am SSOOOOO behind you and really wish I could help! I know Visual Basic, some html, some C++, have played around w/ linux and it's command line etc but....I really am lost here, SO wish I could help! KEEP UP THE GREAT WORK! :) and most of all...

THANK YOU!!! :D
[Touch HD Windows Mobile ROM Development] orux:
pichurri:

I sent a diff to you (private message) yesterday. Could you check it, please?
[Touch HD Windows Mobile ROM Development] body85:
@ jim "ask HTC" was a joke :-)

An yes, THX@all!!!!

WE CAN DO IT!
[Touch HD Windows Mobile ROM Development] jim256:
Haha ok I honestly couldn't tell!! I thought maybe (what w/ the wink an all but...) lol sry!

Anxiously waiting!... :)
[Touch HD Windows Mobile ROM Development] pichurri:
I answered the PM, :)!!!

Have you seen this thread and wiki, it could be useful on finding how wince does to draw into the screen:

http://xdaforums.com/showthread.php?t=442712

http://wiki.xda-developers.com/index.php?pagename=Developing a graphics driver for Windows Mobile

cya
[Touch HD Windows Mobile ROM Development] xmoo:
I'm in Barcelona now.

I will try to me active as much as I can!
[Touch HD Windows Mobile ROM Development] JohnQ:
hey, xmoo, you in barcelona to attend to the mobile world conference?
[Touch HD Windows Mobile ROM Development] xmoo:
Nope,

When ist that??
[Touch HD Windows Mobile ROM Development] Rayzer HD:
Its from 16. to 19. february :)

Rayzer HD
[Touch HD Windows Mobile ROM Development] Ryu Kenshin:
xmoo will represent xda android community in mobile world conference to question both HTC and Google for their lack of support, hahaha :D
[Touch HD Windows Mobile ROM Development] torespen:
Same as with everybody else here, hangs on loading..

Norwegian Touch HD, org. ROM

Just to let You guys know :)

(yes yes, know tht peeps are working on it.. read all pages ;) )
[Touch HD Windows Mobile ROM Development] xmoo:
Someone has the adres or something?? OR web adres so I sign myself up to go there.
[Touch HD Windows Mobile ROM Development] surfaholic:
http://www.mobileworldcongress.com/
[Touch HD Windows Mobile ROM Development] BigDaemon:
Have fun there xmoo and if you have the chance, talk to some Android-developers how to solve our display-problem ;-)

By the way: Anyone got something new?? First time since a long time that this thread wasn´t on page 1 :P
[Touch HD Windows Mobile ROM Development] xmoo:
Damnn the prices are sick :S
[Touch HD Windows Mobile ROM Development] torespen:
Damn!!... Does that include free bar, limo, and hookers? :D
[Touch HD Windows Mobile ROM Development] gerdgerdgerd:
i believe it includes a touch hd :D
[Touch HD Windows Mobile ROM Development] BigDaemon:
DAMN, i just looked at the prices, are they crazy?? :-O

But whats even more interesting: Any news on the Framebuffer/Display-Driver?? Anyone got something new??
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
These conferences are ment for just the bussines professionals, execs and Press. Not for general public. The price is set like that to ensure that there isn't to much general public comming even if they find a way to fake a bussines or press association.

If you think thats alot of money, try to imagine how much a week long training course at SAP, Cisco, Qualcomm, ... costs, just for the training, your certification isn't included.

Its one of the reasons why people who get allowed to attend these special trainings and conferences by their firms get locked to a contracts with pritty hefty penalties when you leave to soon regardles.

In the case of something like SAP, the difference between having training and certification and not having either is that without you make about 3000€ a month as a sysadmin and once you have that training and certification, you get upgraded to 5000+ within the first year and closer to and over 10k€ per month within the next 2 to 5 years, depending on how good you are.

Putting things in perspective like that would make the price for this conference be just a small expence for a company compared to the wages the professional already has.

And as for the execs going to these things. They have 5 and higher figure salaries per month to start with, most of their restaurant bills are more expensive then going to this conference ...

Anyways, back on subject. I'm working on a Gentoo based ARM kernel for the blackstone.

If it works, I'll be able to recompile and reconfigure kernels at a retardedly high rate sure to give us a faster result in getting a viable kernel up and running.