yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] sjs:
i'll keep that in mind. ;)

i should be able to help with this over the weekend.

started at http://wiki.xda-developers.com/index.php?pagename=BlueangelGPIO ... we should probably start Blueangel pages as they have for Himalaya like BlueangelHardware, etc.

not much, but a start.
[Windows Mobile Development and Hacking General] cr2:
> The ASIC is for GPIO and SDIO and is located at physical 0x0D800000.

> Well it seems this ASIC is not used for

> the SD interface, but one at 0x0C800000

Our numbers are 0x0e000000 and 0x0c000000. Since we are only two bits away, my next guess will be that

ASIC3 SDIO is used. That will also explain why there is no [SDIO] ATI section.

Corrected memory map:

Physical Virtual Size ? Description

0x00000000 0xa0000000 0x200000 PXA263 StrataFlash ROM 32Mbyte

0x48000000 0xa8100000 0x100000 PXA263 Memory Controller

0x16000000 0xa9000000 0x010000 Debug port

0x04000000 0xa9100000 0x100000 Disk on chip ?

0x0e000000 0xa9200000 0x010000 ASIC3 SDIO

0x0c000000 0xa9300000 0x010000 ASIC3 GPIO & misc.

0x11000000 0xa9400000 0x010000 unknown

0x10000000 0xaa000000 0x000000 USB +256b, BTUR +36b -> 0xaa050000

0x10800000 0xaa100000 0x000000 HTC DPRAM ASIC P/N: 30H80037-00-L

0x08000000 0xab000000 0x400000 ATI Imageon 3200

0x20000000 0xac000000 0x010000 pcmcia0

0x28000000 0xac100000 0x010000 pcmcia0

0x2c000000 0xac200000 0x0E0000 pcmcia0

0x30000000 0xad000000 0x010000 pcmcia1

0x38000000 0xad100000 0x010000 pcmcia1

0x3c000000 0xad200000 0x0E0000 pcmcia1

0x40000000 0xae000000 0x200000 PXA263 Peripherals (ser0,ser1)

0xa0000000 0xb0000000 0x400000 SDRAM 64MB

0xa4000000 0xb4000000 0x400000 SDRAM 64MB[/quote]
[Windows Mobile Development and Hacking General] cr2:
Running haret over wireless i get the flood

of the GPLR[86] GPLR[87] GPLR[88] changes.

HaRET(7)# dump gpio

GPIO# D S A INTER | GPIO# D S A INTER | GPIO# D S A INTER | GPIO# D S A INTER

------------------+-------------------+-------------------+------------------M

0 I 1 0 RE FE | 24 O 0 0 | 48 O 1 2 | 72 I 1 0

1 I 1 1 | 25 O 0 0 | 49 O 1 2 | 73 O 1 0

2 I 1 0 FE | 26 O 1 0 | 50 O 0 0 | 74 O 1 0

3 I 0 0 RE | 27 I 0 1 | 51 O 0 0 | 75 I 1 0

4 I 0 0 RE | 28 O 0 1 | 52 O 1 2 | 76 I 1 0

5 I 0 0 | 29 I 0 2 | 53 O 1 2 | 77 I 1 0

6 I 1 0 | 30 O 1 0 | 54 O 0 0 | 78 O 1 2

7 I 0 0 | 31 O 0 1 | 55 O 1 2 | 79 O 1 2

8 I 1 0 RE FE | 32 O 0 1 | 56 I 1 1 | 80 O 1 2

9 I 0 0 RE FE | 33 O 1 2 | 57 I 0 1 | 81 O 0 1

10 I 1 0 RE FE | 34 I 1 1 | 58 O 0 0 | 82 O 1 1

11 I 1 0 FE | 35 I 0 1 | 59 O 0 0 | 83 O 0 1

12 O 0 0 | 36 I 1 1 | 60 I 0 0 | 84 I 1 2

13 O 0 2 | 37 O 0 0 | 61 O 1 0 | 85 I 1 0

14 I 0 1 | 38 I 1 0 RE FE | 62 O 0 0 | 86 I 1 0

15 O 1 2 | 39 O 1 2 | 63 I 1 0 | 87 I 1 0

16 I 1 0 FE | 40 O 1 2 | 64 O 0 0 | 88 I 1 0

17 I 1 0 FE | 41 O 0 2 | 65 O 0 0 | 89 I 0 1

18 I 1 1 | 42 I 1 3 | 66 I 1 0 | 90 I 0 0

19 I 0 1 | 43 O 1 3 | 67 I 0 0 | 91 I 0 0

20 O 0 0 | 44 I 0 3 | 68 I 1 0 FE | 92 I 0 0

21 O 0 0 | 45 O 0 3 | 69 I 1 0 FE | 93 I 0 0

22 O 0 0 | 46 I 1 2 | 70 I 1 0 | 94 I 0 0

23 O 1 0 | 47 O 0 1 | 71 I 1 0 | 95 I 0 0

Triggered changes:

GAFR[23] changed to 2

GAFR[24] changed to 2

GAFR[25] changed to 2

GAFR[42] changed to 3

GAFR[43] changed to 3

GAFR[44] changed to 3

GAFR[45] changed to 3

GPDR[113]

GPDR[17]

GPDR[43]

GPDR[45]

GPDR[75]

GPLR[0]

GPLR[112]

GPLR[113]

GPLR[119]

GPLR[120]

GPLR[16]

GPLR[17]

GPLR[23]

GPLR[24]

GPLR[25]

GPLR[27]

GPLR[2]

GPLR[31]

GPLR[3]

GPLR[42]

GPLR[43]

GPLR[44]

GPLR[56]

GPLR[75]

GPLR[84]

GPLR[85]

GPLR[86]

GPLR[87]

GPLR[88]

GPLR[96]

GPLR[98]
[Windows Mobile Development and Hacking General] cr2:
Updated GPIO wiki.

Don't see any SD events.

Will manually dump the ASIC3 registers :(
[Windows Mobile Development and Hacking General] sjs:
heh i've got my share of acronyms to sort out with that page now. between the arm arm and pxa26x dev manual i thought i would learn them all. but then, i'm still not finished either of those yet.

yikes!
[Windows Mobile Development and Hacking General] cr2:
Another interesting thing to test is the DPRAM size. haret can write a pattern block into this 64K address range and

look how much can be seen.

Hopefully we don't destroy the GSM module. Another option is to issue the

AT%DPRAMTEST=1 RIL command

and look at the memory, but it means

wince programming :(
[Windows Mobile Development and Hacking General] cr2:
SSP Ports:

16 bit MOT 921600bps

16 bit TI 230400bps
[Windows Mobile Development and Hacking General] sjs:
using GNU screen and saving a hardcopy is an easy way to save the dumps but if you want to dump to file using [PV]DUMP (for easy diff'ing) then here's a patch:

http://web.uvic.ca/~sjs/script.cpp.patch

i'm also thinking about doing a quick and dirty file manager for PPC on linux... it's tedious typing each filename with full path. :( even something that just runs the current 'p*' synce-rapi2 programs in python/gtk or something. if it will list files, let me cd and then pcp to $PWD i'll be happy.
[Windows Mobile Development and Hacking General] cr2:
I was logging the haret 'pd' output, but

the dedicated haret script showing the

registers would be better.

There is no support for watching the

ASIC3 GPIOs :(

Keep an eye also on

http://www.handhelds.org/moin/moin.cgi/HpIpaqHx4700Hardware
[Windows Mobile Development and Hacking General] cr2:
GPIO wiki updated. Looks much better now.
[Windows Mobile Development and Hacking General] sjs:
what changes when inserting/removing an SD card in ASIC3:

NO SD CARD WITH SD CARD
0x0e000243 = 0 0x1f
0x0e00024a = 0 0x02

also, updated BlueangelGPIO. ASIC3 SDIO uses gpio pin 11.

seeing as handhelds.org is part of google's summer of code -- http://code.google.com/summerofcode.html -- i am now seriously considering quiting my job in order to work on this port most of my time. it's not just the $4500 i could make, but this would be much more fun than cooking at boston pizza. still so much to learn though....
[Windows Mobile Development and Hacking General] cr2:
It is interesting that there are not a lot

of them, given the multiplexed nature

of this interrupt.

The gpio tracing code in haret is SO primitive (busy loop), that it's not a big deal to add the "DUMP ASIC3"

and "WASIC3GPIO" commands.

It's doable, if you'll first put aside running the phone. The real 31337 project is to adapt the wine loader for wince

(like it is done in mplayer) and to rearrange the wine dlls into coredll & friends.

But it's not for three months.

I'm very busy in the university, but don't mind to ask for help.
[Windows Mobile Development and Hacking General] sjs:
right now because of all the hard resets w/ haret i have been using my crummy nokia 3xxx mobile. so this isn't a huge deal, but....

When I started the application for google's SOC today I realized that 3 months is pretty unrealistic. would've been nice to get paid for doing something fun, but i can do it anyways and i don't need the $.

i'll probably still be here asking you questions as soon as I get a little more involved in this. thank you for the kind offer. :)
[Windows Mobile Development and Hacking General] cr2:
With AllocPhysMem() in wince4 m$ gave

us a nice interface for loading the kernel.

Unfortunately, the linker rejects to link.

MSDN documentation says that the -DWINCEOEM=1 should

be added to the command line. Then

i hit the nonexisting headers.

It seems that they have obfuscated the

function call to complicate our life...
[Windows Mobile Development and Hacking General] cr2:
Was my fault :) Found another nice function

ForcePageout().

The code now looks like that:

ForcePageout();

kernel_bundle=(uint8 *)AllocPhysMem(kbsize + 4095,PAGE_EXECUTE_READWRITE,0,0,&pkernel_bundle);

The remaining headache is the busmaster DMA by ATI Imageon to 0xa00c0000. Probably we shall simply disable granting it. The better solution is to relocate the

kernel to 0xa0200000 instead of 0xa000000, but it may require changes in the kernel code. It seems that the Himalaya LCD init code and the TSC2000 code can be reused, and the hx4700 guys are also moving forward. Time to request the MACH_BLUEANGEL :)
[Windows Mobile Development and Hacking General] sjs:
hmmm... i'm downloading the wince sdk for 4.2 now to see if i can get my hands on psyscall.h and pkfuncs.h. where did you find these headers? i had a look through viewcvs on hh.org but didn't find anything promising for ce headers. googling only gave me some outdated links for ce3 on itsme's site.

that's great we can use the himalaya lcd/touch screen code. the keyboard we'll have to do ourselves, correct? i don't believe the himalaya has one but i'm not sure.

are there certain requirements before requesting a machine type? i've registered on arm.linux.org.uk so give me the word and i'll register mach_blueangel right away.

all this... and i've got a linear algebra exam tomorrow. i have a feeling i might not do so well... 8)
[Windows Mobile Development and Hacking General] sjs:
last line of linux/arch/arm/tools/mach-types generated from http://www.arm.linux.org.uk/developer/machines/?action=download:

blueangel	MACH_BLUEANGEL	BLUEANGEL	766

8)
[Windows Mobile Development and Hacking General] cr2:
You don't need the headers. Adding

extern "C" void ForcePageout(void);

extern "C" LPVOID AllocPhysMem(DWORD cbSize,DWORD fdwProtect,DWORD dwAlignmentMask,DWORD dwFlags,PULONG pPhysicalAddress);

is enough. If you know that, then you are WINCEOEM :) The gx.dll is not available

in the standard WCE420. Use PC2003 instead. Actually, the right way is what

betaplayer is doing:

#define GETRAWFRAMEBUFFER 0x00020001

#define FORMAT_565 1

#define FORMAT_555 2

#define FORMAT_OTHER 3

typedef struct _RawFrameBufferInfo

{

WORD wFormat; // =1 (iPAQ hx4700)

WORD wBPP; // =16 (iPAQ hx4700)

VOID *pFramePointer; // =0x4A800000 (iPAQ hx4700)

int cxStride; // =2 (iPAQ hx4700)

int cyStride; // =960 (iPAQ hx4700)

int cxPixels; // =480 (iPAQ hx4700)

int cyPixels; // =640 (iPAQ hx4700)

} RawFrameBufferInfo;

RawFrameBufferInfo rfbi;

HDC hdc = GetDC(NULL);

ExtEscape(hdc, GETRAWFRAMEBUFFER, 0, NULL, sizeof(RawFrameBufferInfo), (char

*) &rfbi);

ReleaseDC(NULL, hdc);

unsigned short *vram_address;

vram_address=(unsigned short *)rfbi.pFramePointer;

#define GETGXINFO 0x00020000

typedef struct GXDeviceInfo

{

long Version; //00 (should filled with 100 before calling ExtEscape)

void * pvFrameBuffer; //04

unsigned long cbStride; //08

unsigned long cxWidth; //0c

unsigned long cyHeight; //10

unsigned long cBPP; //14

unsigned long ffFormat; //18

char Unused[0x84-7*4];

} GXDeviceInfo;

Himalaya has the same TSC2000 chip and

the atihwtbl0.txt is very close. hx4700 is

even using the w100fb accelerated FB driver. We only need to find out the ASIC3 GPIO setup.

Unless you are asked about the

Jordan normal form eigenvectors, when the multiplicity

>1, then linear algebra is easy 8)

Good luck!
[Windows Mobile Development and Hacking General] cr2:
Ok. handhelds.org will eventually pick it up.
[Windows Mobile Development and Hacking General] sjs:
riiiight, because it's all in coredll.lib. thanks.

if haret's penguin graphic has been running fine then gx.dll should already be on my device, no? ... i've got 4.21 installed which is wm2003, which is ppc2003 smartphone, right? i have to admit i'm confused between all these names MS keeps coming up with. :?

ah, i was not aware the tsc2000 is a keyboard controller as well.

thank you! i've got an hour of study time left... and it really isn't hard, but this is the first time i'm reading some of this material. :oops: ... i guess my practice excercises will be the exam. luckily this is just intro to L.A.
[Windows Mobile Development and Hacking General] cr2:
There are three (different) include and lib trees

STANDARDSDK_420

SMARTPHONE 2003

POCKET PC 2003

First i have tried the STANDARDSDK_420,

but could not link, so i have changed to

POCKET PC 2003.

BTW, Blueangel and Himalaya are NOT smartphones, at least, only the POCKET PC 2003 eVC tools are working properly.

I'm compiling with wine, so it doesn't really matter 8)

Himalaya doesn't have a keyboard. I don't know how and where the keyboard is hooked. There is a PIC controller on the board with an unknown function. Maybe it serves the keyboard, but we will probably never know unless the keyboard driver is forced to tell us :)
[Windows Mobile Development and Hacking General] sjs:
thanks for clearing that up.

sorry, i mistakingly read a TI page on the tsc2200 (which includes a keyboard controller) and thought i was reading about the tsc2000.

no matter which implementation of memPhysMap() I use haret seems to freeze randomly anyways, using VirtualFree or not. :? i should probably figure out exactly what these functions are doing... might get rid of the cache to KISS while i learn about them.
[Windows Mobile Development and Hacking General] cr2:
IMO, memPhysMap is a big hack.

There are three ways to avoid it:

1. replace

malloc/free in the garbage collector by

VirtualAlloc/VirtualFree and then call LockPages to get the PFNs.

It doesn't require any substantial changes

in the program

and is very portable. Will work even on

wince 2.11

2. Use GetKPhys. I didn't try it. If it gives

the physical pages, how to map then into

the virtual address space ? With VirtualAlloc/VirtualCopy ? Seems to be too tricky.

3. Use AllocPhysMem() Gives the

continuous memory pool, so no MMU games are necessary, but can fail (unlikely on a 128MB machine, i have allocated 24MB without any problems on BA with 64MB allocatable RAM). Works only on wince >4.00. Since we have 2MB wince kernel RAM and 64MB ramdisk at the bottom no address overlap can happen.

So, the first way is the best for the humankind, requires only minor changes, but is not easy to debug when things fail.

The third way means some major rewrite, but should work.

IMHO the preloader allocation should happen before the kernel/initrd allocation,

so it will be closer to the memory top.

Calling ForcePageout() before the memory allocation never hurts in any case.
[Windows Mobile Development and Hacking General] cr2:
Both methods work on BA.
[Windows Mobile Development and Hacking General] cr2:
Returns the PFNs like 0x97xxx000.

Don't look like physical addresses.

They are also discontinuous, and

would be really painful to use.
[Windows Mobile Development and Hacking General] cr2:
I have modified the gpio watcher to watch on an arbitrary physical address, disabled

Log(), removed the 'changed to' string

and excessive memPhysMap calls.

It works MUCH faster and reports more

gpio changes. I'd like to get rid of the

time(NULL) calls and replace them with

reading the OSCR register. Should consider

the overflow, though ...

Get this warning:

bw_mem.obj : warning LNK1166: cannot adjust code at offset=0x00001000, rva=0x0000C2B8

This code should be competely removed, not only because it was written by Larry McVoy.

If you can dump and decode the MDCNFG, MSC0, MSC1, ... PXA263 registers, that will be great. Also the ASIC3 gpio/dir/alt registers should be dumped/watched. 16bit weirdness!

It's too late, i'll go home ;-)
[Windows Mobile Development and Hacking General] sjs:
i'd like to see that patch! i have to get an old P3 running (waiting for a couple parts in the mail) because my desktop is now an amd64 and synce doesn't want to compile on this arch. hence me being so quiet this last while; that and real life. school's over in a couple weeks and i'm quiting my job Real Soon(tm) so there might be a week before next semester for me to try some work on this again.

seems we lost him to the 'other side' i guess... open source didn't make him $ so he concludes it doesn't work. :? tell that to mysql and friends... as for us, we have svn. :) never used bitkeeper, maybe it is much better. i digress...

as i said, i'll have an i386 machine to do this with in the next couple weeks so i'll read the wiki and this thread again and do my best to help out!
[Windows Mobile Development and Hacking General] rkde:
Hi

I am a keen user of linux and love the KDE look type and where possible I avoid MS although when I sync my XDA I have to use windows and for this I use win4lin 9x.

I am sure linux would rock on the XDA and would love to see a disto like Mepis with all software included.

I do have some concern about sat nav ie tomtom would we have a linux developer through together some GNU versions where we apply our own maps ie tele atlas or would we have a win4lin 2003** or VM? By the way if there is a disto with everything to include navigation or if tomtom produced a linux version I would be there...
[Windows Mobile Development and Hacking General] JuNu_KN:
I have followed it with high interrest! Are there no mor news on it, or can I follow in an other Thread?
[Windows Mobile Development and Hacking General] sjs:
it seems not many owners of the blue angel are trying to run linux on it. this is the first time i've ever reverse engineered anything significant, so i still have a ways before i contribute anything significant to the effort. cr2 is busy with school as well, though he is making progress!

the going is slow right now, but i am quite determined to do this even if it takes me years.

if you have a device other than the blue angel you may have a much easier time running linux on your device.

mepis? surely you are joking! that is a bit heavy for a pda.

http://handhelds.org is another great resource if you've already read the content on the wiki here at xda-developers.com.
[Windows Mobile Development and Hacking General] Echelon:
IRC Channel for the BLUEANGEL Linux port

Hi

I registered a IRC chanell for this Linux Port .

feel free to /join #blueangel at irc.freenode.com

Regards Echelon - alias rob_w
[Windows Mobile Development and Hacking General] rick83:
Hi guys,

i would like to know how do i port my device over to linux. I am quite interested in doing so.
[Windows Mobile Development and Hacking General] cr2:
I have returned from vacation and added this link

http://www.electronicproducts.com/whatsinside/viewteardown.asp?filename=HTC_XDA_III_web.html

to wiki. Some interesting information

can be seen there.

M24C08-WDW6 EEPROM - 8kBit, Serial I2C

ADCM-2650 Camera - CMOS, VGA 640 X 480

ST3243EB Transceiver - RS232

HTC, HTC_AIC2 ASIC - MPU Timing Generator

M24C08-WDW6 EEPROM - 8kBit, Serial I2C

PIC16LF873A Microcontroller - 8-Bit, Enhanced CMOS Flash

H80037-01 NPI - GPIO & SD/MMC IO Controller - ASIC

RD38F1010C0ZTL0 MCP - 32Mbit NOR Flash and 4Mbit SRAM

It is necessary to understand what I2C

devices are activated, and how the "known" I2S devices are routed and multiplexed:

PXA263, BRF6101, UDA1380, IOTA

The biggest problem for me now is that i have severely damaged

the LCD:

Sony ACX502BMV

If somebody has an idea where i can buy it

in Germany, let me know.
[Windows Mobile Development and Hacking General] matze:
Hello!

I'm keen to get linux to my new T-Mobile MDA III. As a matter of fact this device is the same as an XDA III - BlueAngel.

I followed the instructions at http://wiki.xda-developers.com/index.php?pagename=BlueangelKernel and downloaded all files (compressed kernel image, initrd, haret and the startup file) directly from this page.

After invoking haret in the Windows CE file manager, tux came up and the kernel booted. init was started, too. But the system seems to hang after (or during) starting the portmapper daemon. After a long period of time the screen went black.

I modified the startup file to start /bin/sh instead of init and got a root shell prompt after the kernel boot. But it seems that the keyboard doesn't work yet, thus this result is the same as a frozen system...

Whats the problem? Do I need more configuration stuff?

Thank you.
[Windows Mobile Development and Hacking General] Exarv:
Hi All,

Since 2 weeks I also have a HTC Blue Angel (sold as: SPV M2000)

And offcourse, I want Linux to run on it.

I'm a application developer (Pascal, Delphi, C++)

And have some Linux system administration experience.

Started at Redhat 5 until Fedora Core 4.

I don't have that much experience with programming kernel stuff.

I also have the problem, that the BA appears to hang after loading portmap.

It has nothing to do with the portmap.

When portmap is not started at all (changed the initrd) It hangs at the point, where it normally starts portmap. looking at the /etc/rc2.d dir, portmap should be the last service to start.

When at that stage,

I remove the BA from the cradle, and put ik back in.

I get udc_is_connected returns 1 on the lcd screen.

When running modprobe usbnet on the host,

I get usb0: Full speed config #1: 100 mA, Ethernet Gadget, using CDC Ethernet Subset on the lcd screen.

So appear to me, thatthe BA didn't freeze.

Then running ifconfig usb0 192.168.0.205 up on the host.

And I could login on the BA with ssh root@192.168.0.206.

So the BA does not hang. It's working!

But it's not showing on the screen...
[Windows Mobile Development and Hacking General] cp15:
Correct, the keyboard isn't working yet.

There seems to be no information about it, just on gpio line which signals an interrupt.

I think it is required to reverse engineer the windows driver.

Anyone here who knows more about it?

Therefore it doesn't make sense to run getty or a shell on the framebuffer console.

The disconnect thing is no longer required in the -hh2 kernel, but usb seems still a bit unstable.

Please report yor board id (hopefully shown very early in the bootmessages) to the wiki.
[Windows Mobile Development and Hacking General] Exarv:
Board ID added to Wiki.

I also saw that I didn't have to get the BA out of the cradle and back in to let usbnet work.

Does anybody booted the BA from nfsroot succesfully?

I used the wiki steps for the himalaya, but got the message /dev/nfs was not available.. This needs a kernel recompile, right?

Or is it also possible with a nfs-mount and then a pivot-root in the linuxrc?

before init is started?

Is it already possible to start x-based applications, which are displayed on the framebuffer?
[Windows Mobile Development and Hacking General] cp15:
Thanks.

The kernel for download on the wiki doesn't support root nfs.

Since there are no current diffs, you can not recompile. Sorry, I have to clean up the mess a bit first.

But you can use pivot-root.

It should also be possible to use a (ext2-formatted) SD or MMC card as root filesystem.

The Xfbdev in the ramdisk should work, if you want some applications download the handhelds ipaq h3900 rootfs
[Windows Mobile Development and Hacking General] cr2:
Hmm. Do you have a working asic3 driver ?

Sounds great :)

Still waiting for the delivery of a new LCD.
[Windows Mobile Development and Hacking General] cr2:
I'll have a look at the driver, through somebody with IDA will have more luck.

Is the board id visible in /dev/mem ?
[Windows Mobile Development and Hacking General] Exarv:
You can see what the boardID is by running

dmesg | grep -i boardid

I did manage to pivot_root to a nfs mounted directory.

I found a ext2 image for gpe on http://handhelds.org/~koen/NFSRoot

When I started the /etc/init.d/gpe-dm, I did get something that looks like a GPE login screen on the lCD. But the touchscreen didn't respond.

BTW. Is this site for you also, so very slow? It's even hosted ad xs4all.net (my adsl provider), So I think it's the server itself??
[Windows Mobile Development and Hacking General] cr2:
I need the working LCD first ;)

Yes. It is very slow even at 4:00 in the morning.
[Windows Mobile Development and Hacking General] Exarv:
4.00 am?

Don't think I'll still be working / playing around that time.

maybe offtopic, but:

Who arranged this site?

I have my own company.. We also do hosting based on own servers.

In stead of a donation, maybe we can host this site 'for the community'.

Don't know what the data traffic is, but it's probably faster..