UK carrier O2 has begun offering HTC's year-old attempt to pre-empt the netbook market, branding the 3G-enabled device as the XDA Flint.
The Flint is based around a 5in, 640 x 480 screen and runs Windows Mobile 6.1 Pro on a 624MHz Marvell PXA270 processor. There's an AMD ATI W2284 graphics chip on board too.
O2 XDA Flint O2's …
"There's an AMD ATI W2284 graphics chip on board too."
Is this with drivers, or is it going to be the same situation as all those mobile phones with nVidia GoForce chips where WM is using generic (i.e. non-accelerated) drivers?
AFAIK, users of e.g the Toshiba G900 have been left high-and dry by Toshiba as far as hardware support is concerned.
If it's like any of their other devices the graphics chipset might as well be a simple framebuffer, as they either don't pay for the acceleration SDK or can't be arsed writing a driver.
This is one of the two reasons i'm sending back my Android G1, along with the appalling battery life.
UK carrier O2 has begun offering HTC's year-old attempt to pre-empt the netbook market, branding the 3G-enabled device as the XDA Flint. The Flint is based around a 5in, 640 x 480 screen and runs Windows Mobile 6.1 Pro on a 624MHz Marvell PXA270 processor. There's an AMD ATI W2284 graphics chip on board too. O2 XDA Flint O2's …
"There's an AMD ATI W2284 graphics chip on board too."
Is this with drivers, or is it going to be the same situation as all those mobile phones with nVidia GoForce chips where WM is using generic (i.e. non-accelerated) drivers?
AFAIK, users of e.g the Toshiba G900 have been left high-and dry by Toshiba as far as hardware support is concerned.
HTC suck
If it's like any of their other devices the graphics chipset might as well be a simple framebuffer, as they either don't pay for the acceleration SDK or can't be arsed writing a driver.
This is one of the two reasons i'm sending back my Android G1, along with the appalling battery life.