Database Develop

hacking up our own 3d drivers?

bit of a mad idea, but what is stopping us from hacking up our own 3d drivers? im sure a little probing around the instruction set might yeild something partially useful perhaps maybe? *ooh this interupt turns on the imageon chip!11* etc
thoughts?

Don't see why it can't be done, must be someone out there that is up for the challenge
But as this is an new CPU I would thought it would be difficult as there is no previous version with working drivers to work from, would be amazing is someone did it though

Reverse engineering as proved a daunting task even for the resourceful linux development community. for exemple open source (ie non-vendor provided) nvidia and ati drivers are way poorer performers than their vendor provided binary blobs counterparts.
Qualcomm being actively hostile to open their specs, i doubt drivers could be created in a reasonable time frame.

im half inclined to try

maybe this could help you start...
http://forum.xda-developers.com/showpost.php?p=1643361&postcount=32
(qualcomm brew/opengl dlls with source code)

sweet ill give them a look over - i have quite a bit of experience with opengl but not much embedded experience, ill see what i can do, time permitting
edit: mm not so useful really - having lots of trouble finding any info online too - though i think the gfx is Imageon 2388/2380

If not already posted but. . .

Look at this:
http://gizmodo.com/360514/htc-says-software-fix-is-coming-for-lousy-video-drivers
An official HTC statement about the drivers looks promising. Again, keep your hopes up and guard up!

Not only is this old and posted to death, but
However this fix is not a new video driver to utilize hardware acceleration
Click to expand...
Click to collapse
There is nothing promising about this, please read carefully next time, it just misleads people who read your post

Damn. . . I thought that was a new and updated statement. Look if you only read a little bit of it then you probably missed out on this.
Some of our top engineers have investigated video performance on our devices and have discovered a fix that they claim will dramatically improve performance for common on-screen tasks like scrolling and the like. Their fix would help most of our recent touch-screen products including the Touch family of devices and TYTN II / Tilt, Mogul / XV6900. The update is in testing and we hope to release it soon. However this fix is not a new video driver to utilize hardware acceleration; it is a software optimization. Video drivers are a much more complicated issue that involves companies and engineers beyond HTC alone. We do not want to lead anyone to believe they should expect these. To explain why we are not releasing video acceleration instead of the optimization
I offer you our official statement... "HTC DOES plan to offer software upgrades that will increase feature functionality, over the air wireless speeds and other enhancements for some of the phones being criticized, but we do not anticipate including any additional support for the video acceleration issues cited in customer complaints. It is important for customers to understand that bringing this functionality to market is not a trivial driver update and requires extensive software development and time. HTC will utilize hardware video acceleration like the ATI Imageon in many upcoming products. Our users have made it clear that they expect our products to offer an improved visual experience, and we have included this feedback into planning and development of future products. To address lingering questions about HTC's current MSM 7xxx devices, it is important to establish that a chipset like an MSM7xxx is a platform with a vast multitude of features that enable a wide range of devices with varied functionality. It is common that devices built on platforms like Qualcomm's will not enable every feature or function. In addition to making sure the required hardware is present, unlocking extended capabilities of chipsets like the MSM 7xxx requires in-depth and time consuming software development, complicated licensing negotiations, potential intellectual property negotiations, added licensing fees, and in the case of devices that are sold through operators, the desire of the operator to include the additional functionality. To make an informed decision about which handset suits them best, consumers should look at the product specification itself instead of using the underlying chipset specifications to define what the product could potentially become."
Click to expand...
Click to collapse

~~Tito~~ said:
Damn. . . I thought that was a new and updated statement. Look if you only read a little bit of it then you probably missed out on this.
Click to expand...
Click to collapse
Sorry Tito,
Nothing new to that, just the same old company line that they've been spouting for weeks.

Meeing!! I thought I saw something new. Well Law Suit it is then since they don't want to make a small amount of effort to fix some devices problems that they shouldn't have. I wonder if they use their own devices or do they have drivers made for them and not us?

[DEV] MeeGo for Nexus S (Also, Help Required)

So, I have a barebones version of MeeGo (barely) running on the Nexus S. I can't really do much with it on my own, but I'm posting the info here so you can build it and try it for yourself.
What works:
• ADB root shell
• X11 & UI apps
• Super-AMOLED brightness control (fixed! still off-colour tho…)
What doesn't work currently:
• Touchscreen
• WiFi
• Anything else
If you've never built a MeeGo rootfs before, it's relatively straightforward, and all the binaries are precompiled for you (but it's definitely for developers only).
I have my boot.img (kernel + ramdisk) and a MeeGo kickstart file at http://blog.steventroughtonsmith.com/2011/01/nexus-s-meego.html ; you can use fastboot to boot the image, or flash it to the recovery partition to dual boot. The actual MeeGo rootfs is run from a rootfs.ext2 file you can drop onto the Nexus S using Mass Storage mode - no need for messy flashing or the like, you can thank me later).
There's not much else I can do on my own right now, so if you want to see anything become of this do get involved!
My kernel is stock git://android.git.kernel.org/kernel/samsung.git ; make herring_defconfig; the only change was modifying the .config to turn on CONFIG_VT (needed for X11).
Go nuts!

Well done on the port so far. This is way beyond my area of expertise, but I do hope that some people can help build off of what you've done so far. Always nice to see what kind of fun stuff we can run on these devices...

Looking forward to more development on this!

Great stuff!
I have been waiting for someone to start something like this, I work as an embedded developer during the day so not much time at night but I will chip in were and if I can, I am pulling the source and looking at the build system / process.
Looks like you have done the heavy lifting of bootstraping the device now its just about porting drivers.
Cheers and great start!

What driver are you using for the X11 and is it accelerated?

ilfccd said:
What driver are you using for the X11 and is it accelerated?
Click to expand...
Click to collapse
It's using unaccelerated graphics; although, with luck, SGX 540 graphics drivers are available for other devices (like the OMAP4) so in theory you may be able to patch those to run.

Update - backlight working; color is still fscked, might be gamma:

According to PowerVR rep on CES there should be an open source driver later this year (info from Phoronix, but they are lately not really reliable source of info).
Here is another question though. Have you tried using the omap tree of linaro for the kernel build?
I don't have Nexus S around currently and I'm doing all my work on TI OMAP (A8) based IGEP v2 board and TI OMAP 44xx Panda (A9) board. As they both have PowerVR 530/540 graphics I'll check tonight or tomorrow if the closed driver is compatible with linaro's kernel as I'm currently running that on the IGEP. As Samsung is part of linaro, there could be some patchests for the hummingbird in there. The current uname -r for the linaro is: 2.6.35-1008-linaro-omap so it could be compatible w/ MeeGo's kernel, there could be even newer version in the git tree.
Keep up the great work, I'm really interested in what you are doing with MeeGo. Thanks!

ilfccd said:
According to PowerVR rep on CES there should be an open source driver later this year (info from Phoronix, but they are lately not really reliable source of info).
Here is another question though. Have you tried using the omap tree of linaro for the kernel build?
I don't have Nexus S around currently and I'm doing all my work on TI OMAP (A8) based IGEP v2 board and TI OMAP 44xx Panda (A9) board. As they both have PowerVR 530/540 graphics I'll check tonight or tomorrow if the closed driver is compatible with linaro's kernel as I'm currently running that on the IGEP. As Samsung is part of linaro, there could be some patchests for the hummingbird in there. The current uname -r for the linaro is: 2.6.35-1008-linaro-omap so it could be compatible w/ MeeGo's kernel, there could be even newer version in the git tree.
Keep up the great work, I'm really interested in what you are doing with MeeGo. Thanks!
Click to expand...
Click to collapse
I'm not sure how compatible the kernels will be, the Hummingbird is not an OMAP device (and it would be more akin to the OMAP3 than OMAP4); but if the kernel works, then it should work with MeeGo too. MeeGo is relatively versatile.
Graphics drivers would be nice!

I actually use the linaro distro (ubuntu essential, which i hate) to build meego inside it, because of the work the linaro guys did on the gcc compiler (should be better versed for arm chips). according to the wiki here https://wiki.linaro.org/Platform/UserPlatforms/2010-09-13
the drivers for omap3 should be freely accessible (the 530 core). there is a mention of the 540 core in there also, but I haven't really used them as I don't run X on the boards. You could try the PVR 540 driver for the OMAP4, you might be lucky with the build, could be compatible with the one in the hummingbird. If it is, this could potentially be far better than the Nexus and HD2 MeeGo 'ports' .

ilfccd said:
I actually use the linaro distro (ubuntu essential, which i hate) to build meego inside it, because of the work the linaro guys did on the gcc compiler (should be better versed for arm chips). according to the wiki here https://wiki.linaro.org/Platform/UserPlatforms/2010-09-13
the drivers for omap3 should be freely accessible (the 530 core). there is a mention of the 540 core in there also, but I haven't really used them as I don't run X on the boards. You could try the PVR 540 driver for the OMAP4, you might be lucky with the build, could be compatible with the one in the hummingbird. If it is, this could potentially be far better than the Nexus and HD2 MeeGo 'ports' .
Click to expand...
Click to collapse
I'd try the OMAP4 driver if it was easy to get! I can only find instructions for the PandaBoard, and no repo or download links.

I will try too, if I can't locate them myself will ask someone there. First of all I have some urgent IPoIB business to attend to, though. Probably later tonight or sometime tomorrow.
Edit:
I forgot to ask, did you build MeeGo from scratch or only the kernel and used the daily userland from the arm tree?

ilfccd said:
I will try too, if I can't locate them myself will ask someone there. First of all I have some urgent IPoIB business to attend to, though. Probably later tonight or sometime tomorrow.
Edit:
I forgot to ask, did you build MeeGo from scratch or only the kernel and used the daily userland from the arm tree?
Click to expand...
Click to collapse
Prebuilt userland, no compiling required. I always use the daily RPMs (when the repo is working…)

google just released new graphics driver dunno if that will help your screen problems https://groups.google.com/group/android-building/browse_thread/thread/90d5498622a6ea4

As far as I've seen this was the most promising thread about porting meego here..
So I would suggest to just contact the ones who dived deeper into the matter and even made some progress.
Thread: http://forum.xda-developers.com/showthread.php?t=764255

tomqman said:
google just released new graphics driver dunno if that will help your screen problems https://groups.google.com/group/android-building/browse_thread/thread/90d5498622a6ea4
Click to expand...
Click to collapse
Unfortunately the graphics driver they released is specific to Android, and Android's version of libc. I don't believe there's a way to get that running on GNU/Linux or MeeGo :-(

Being the noob I am what is meego?

tominater12 said:
Being the noob I am what is meego?
Click to expand...
Click to collapse
Nokia (and Intel)'s future smartphone/tablet platform. A real Linux distribution designed for mobile devices, entirely new touch based UI, GPU acceleration, multitouch, etc.

Whoever gets this done gets a beer from me I am really excited about meego but I wont be able to buy the n9 because im on contract untill march next year. If you can get this to run on the nexus s than it should run on the sgs too, that way I can use meego wothout buying a new phone Keep it up

tomislavp4 said:
Whoever gets this done gets a beer from me I am really excited about meego but I wont be able to buy the n9 because im on contract untill march next year. If you can get this to run on the nexus s than it should run on the sgs too, that way I can use meego wothout buying a new phone Keep it up
Click to expand...
Click to collapse
Am hoping to have it up and running on the HD2 first, and then hopefully some of the work we do for that will port over to the Nexus S. Can't wait for the N9…

[Petition] For Nvidia to release tegra2 sources

http://www.change.org/petitions/nvidia-useful-driver-for-tegra-2-chipset#
just thought id share it in here guys. even if you dont think its relevant to you, since you dont flash roms (which is unlikely, because you would not be in xda..lol ), still sign it ! its important stuff, especially if we want a good ics rom.
cheers

xilw3r said:
http://www.change.org/petitions/nvidia-useful-driver-for-tegra-2-chipset#
just thought id share it in here guys. even if you dont think its relevant to you, since you dont flash roms (which is unlikely, because you would not be in xda..lol ), still sign it ! its important stuff, especially if we want a good ics rom.
cheers
Click to expand...
Click to collapse
Note from Nvidia about drivers
Hello Android Development Community
We appreciate all the interest and passion surrounding the NVIDIA Tegra Platform and we take our support for the development community seriously. NVIDIA has been working with Google and Motorola to provide the open source community with the required drivers and other binary code to build full Android OS images for the Tegra 2 powered "Motorola Xoom". We expect Google to make those components available as part of the Android Open Source Project soon.
In addition, NVIDIA is working on a full release of Ice Cream Sandwich (ICS) for our Tegra 2 Dual Core and Tegra 3 Quad Core reference devices to be made available early next year. This release package will comprise of binary code, drivers developed on our reference platforms and any patches necessary to ensure stability & performance with ICS. We hope the open source community can leverage this release for their work on all Tegra devices.
Andrew Edelsten
Source: http://forum.xda-developers.com/showthread.php?t=1309620
These petitions are of no use. The only option we have is to wait.

i know i know... online petitions dont accomplish anything.. but i guess im just a bit desperate.
ive seen that statement and what troubles me is that it mainly concerns xoom which is actually using a different kind of tegra2, ventenara or sth like that whereas 2x has harmony tegra 2, so if nvidia releases drivers for xoom, we wont have much use of them

[DEV] Atrix : Voodoo Sound similar method / Its a WM8993!

Hello all,
According to my depth researches, I'v summed up bits into a package:
- Atrix MB860 does have Wolfson WM9803L DAC chip. (1-?) (Even though all Tegra 2 AP20H should have the same SoC, but after a lot of questions, AP20H {Ventana} stands out for handheld performance (CPU, GPU), power only) Update: Wrong!
- The Asus Transformer uses Tegra 2 T20 , Wolfson WM9803L chip. Does have Voodoo sound support. Based on V1 voodoo drivers.
- I'v got into the same confusion about the 'L' in 'WMxxxxX'; The DAC is based on 2 revisions, both ends with L. Useless
- They both use same SoC implementation, very similiar drivers, nearly same headers. (Based on my own research.)
- Supercurio did not support the Atrix 4G, due its locked bootloader based on the V1 driver date of WM8903L. (So, he might not look back, Wolfson's WM1811 on the road) Update: Atrix 4G = Optimus 2x/Galaxy R
I know I might seem like asking questions, but it should also be considered as a dump project based on both devices. Plus, opening opportunities on other Tegra 2 hard/soft-ware porting.
I don't agree with the idea ignoring 1+ yr old phones with such capabilities...
I consider it just like the fame of the Gi9000, <<<Voodoo = major plus.
P.S. : Supercurio once stated that, Atrix 4G has a diff implementation... Though, after chatting over the IRC, he stated that he do not touch locked bootloader based phones. Thats totally different story. Diff implementation means indirect hardware access, using NVRAM i2c communication (registers)
Big thanks for supercurio, making our phones more valuable. Not anymore... -__-
Thank you all
I will appreciate any help/comment/feedback/correction/response.
Click to expand...
Click to collapse
Thats Bla bla bla above...
Conclusion: Voodoo sound is communicating with #? low level registers with the DAC. Same as what ALSA mixer do when modifying STdac (ICS leak). Unfortunately, Atrix uses OSS on GB, or barebone ALSA thought thats not a problem.
Project STATUS:
Found the right DAC, its WM8993!! Developers/Anyone try Optimus 2x Voodoo sound driver using the patch, patch it to the kernel (WIP)... Loading Voodoo Sound Plus modules didn't work :/
Alternative to Voodoo app coming soon for Atrix/Optimus2x/GalaxyR Tegra 2 Ventana
Workaround for ICS Leak kernel and Kernel 3.x (that includes tiny-ALSA), install AlsaMixer from Play, modify STDac Only While listening to music (be sure not to leave the head/earphones on) to 15. Now you can drive 300 ohms headphones (Though its still limited, shows 10db but not exact) Note: When you remove the earphones or stop music for 5 secs, settings will revert.
List of the confusing/wrong info about Tegra 2 DAC links:
http://forum.xda-developers.com/show....php?t=1124198 Those guyz heard from Androud forums lol
http://www.head-fi.org/t/549644/moto...-sound-quality That guy heard from xda! ^
http://androidforums.com/motorola-at...ola-atrix.html Those are the guilty ones (kidding ), they referred to Tegra 250, thats Harmony used in Tablets not Vantanna 250. :silly:

Having Voodoo sound on the Atrix would be great! I had a Samsung Vibrant before my Atrix, and Voodoo sound was pretty nice! I really like how it sounded and all the settings that it had.
One that i miss for sure is the ability to make the sound mono. I haven't found how to do it on my Atrix yet.
Keep the good work dude! Hope to see it done soon! If it can be done.

I'll be glad to see voodoo sound capabilities on my atrix.Wish you can port this without any problem.
MB860 cihazımdan Tapatalk 2 ile gönderildi

WOOOOOO!! YESSSS!! FINALLY!! I know its not ready, but thank you for looking into it!

djluis48 said:
Having Voodoo sound on the Atrix would be great! I had a Samsung Vibrant before my Atrix, and Voodoo sound was pretty nice! I really like how it sounded and all the settings that it had.
One that i miss for sure is the ability to make the sound mono. I haven't found how to do it on my Atrix yet.
Keep the good work dude! Hope to see it done soon! If it can be done.
Click to expand...
Click to collapse
Mono can be done as a software wise.
Use Poweramp, it has the mono DSP feature.
Good luck.

As stated guys, still haven't got my Atrix, and wish me a luck getting it .91 bootloader :/

bets of luck!! and it will be one hellova feat if u can pull this off ... i have used sgs, nexus s and sgs2 with voodoo ( yes i have purchasrd it from market )... and it makes them a formidable music player rival... i'd really really love to see it for ATRIX also

My friend had this on his Samsung Galaxy Tab and I have been jealous of him ever since lol. I was hoping someone would port it but had given up. I'm glad to see someone is on the case!
Sent from my MB860 using xda app-developers app

Guys, I need your help.
Test this: https://play.google.com/store/apps/details?id=zausan.zdevicetest&hl=en
Or at Play store: Z-DeviceTest
I wan't an info about the DAC. Since i still don't have my Atrix 4G.
Just curious about the WM8903, this info was based on some rumors, a confirmation surely helps, since most tegra 2 ap20h are based on WM8990
EDIT: My Atrix is comming after 2 days...

what to check with that app ?
plus i found some things that u might want to read..( or already read it )
http://forum.xda-developers.com/showthread.php?t=1124198
http://www.head-fi.org/t/549644/motorola-atrix-sound-quality
http://androidforums.com/motorola-atrix-4g/265304-wolfson-audio-hub-hd-motorola-atrix.html

I have downloaded that app but i can't find anything about the DAC...

raghul said:
what to check with that app ?
plus i found some things that u might want to read..( or already read it )
http://forum.xda-developers.com/showthread.php?t=1124198
http://www.head-fi.org/t/549644/motorola-atrix-sound-quality
http://androidforums.com/motorola-atrix-4g/265304-wolfson-audio-hub-hd-motorola-atrix.html
Click to expand...
Click to collapse
Yes I already read it
However, the last link was a guess before the Atrix release i guess, though, what they said is about the Tegra 250 T20 not the A20HP...
All T20 has the WM8903L, while all the A20HP has the WM8990. Thats the confusing part, however, when i get the Atrix, Ill be analyzing the implementation they are using... Might be indirect driver, but i dont think so (Inside a SoC=Direct)
Confusing topic also: http://www.androidtablets.net/forum/shenit-com/18404-tegra-t250-vs-tegra-t20-same-thing.html
What also worries me about the Moto X2. It does have Tegra 2 Ventana. No voodoo sound support, or at least DAC lookout. I don't think there is any A20HP with WM8903 (Does moto play with the sound layer? It should be strict since its a SoC)
I'm not sure between an implementation fault, or lack of support (VoodooSound author). (Though the GS is old)...

Dude, tell me if there is any way i can help you. This is something i really want to help with this project.

Now this is the way for the diff. between T20/T2 ...
http://www.toradex.com/Products/Colibri/Modules/Colibri-T20
And guys, this thread is leaning towards dumping, which clarification can be simplified by yes or no (nothing new), due to poor documentation etc...
And please, can anyone test this https://play.google.com/store/apps/details?id=zausan.zdevicetest&hl=en
It only shows the DAC name on SoC based systems...
Worked with Galaxy R. Result: WM8990 ...
Can't wait to get the Atrix. I'm eager about it...
Plus, I won't lean to the software part, only hardware.
In case it needs to be re-developed, I will work only on the driver. (More to C orientation / kernel...)
Edit: okay, thanks Night Walker! ! For testing the app

Okay guys,
Anybody owns one of these devices except the Atrix:
T2-A20HP:LG Optimus 2X, Motorola Atrix 4G, Motorola Droid X2, Motorola Photon, Samsung Galaxy R, Samsung Captivate Glide
Other: i9023, i9000, Galaxy Tab.
If yes, try the same app above, seems the only app that shows the chip info through alsa...
O2X uses different implementation, thats why supercurio gave a deep shot supporting it, even though, it only supports bits of the original voodoo capabilities...
Can't wait for the new Kaudio driver, might work with the Atrix with no SoC mods.
Just another sound driver made specifically for voodoo. (LG uses its own implementation to the DAC, its driver)

Here is a screen shot of the sound section of that app on my atrix running paranoid android 1.9.5

r3xx3r said:
Here is a screen shot of the sound section of that app on my atrix running paranoid android 1.9.5
Click to expand...
Click to collapse
Same as yours on neutrino 2.8.
MB860 cihazımdan Tapatalk 2 ile gönderildi

K, the Atrix 4G has a different driver...

Tpr0,
I'm unfortunately not a dev, but is there any way I can help with this project?

Guys, sorry for the delay, got ill. And yes, I know your intentions towards support...
I still haven't got my hands 'tight' on the project, got distracted by setting it up... (the Atrix kernel compilation errors)
Anyways, thanks guys, it certainly needs a (low level dev. me) I'm not a high-level programmer, more into hardware level (intermediate) But this project doesn't seem hard to accomplish, but poor documentation does it... ( IT is based on low level programming )