01:04.49 | *** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox) |
01:14.30 | *** join/#openjtag bullet (n=bullet@196.210.62.81.cust.bluewin.ch) |
03:17.01 | AchiestDragon | burst speeds of 6 to 10 mhz maybe posible but to get it sustained at that would not be ,, , and even shourt bursts could have interuptions that delay it |
03:19.26 | AchiestDragon | i have the other problem with the geep-b , in that the ram bandwith is 100mhz for burst access thats 1 16bit read ,, so in actual fact it would be posible to achive a 1.6Ghz but the fpga is not fast enough to cope with that |
03:21.47 | AchiestDragon | it will do 125mhz ,, and by using a cpld it could be posible to dubble that and get 250mhz but as long as it can do 60mhz jtag clock that should be fine |
03:24.14 | AchiestDragon | at the moment its down to coding ,, im working on the avr supervisor program for it atm and still the host code to start on , as well as the vhdl and code for any softcore |
03:24.57 | AchiestDragon | the avr code is beeing written in asembly |
05:12.16 | *** join/#openjtag toi (n=pleemans@d5152D3B4.access.telenet.be) [NETSPLIT VICTIM] |
05:14.11 | *** join/#openjtag toi (n=pleemans@d5152D3B4.access.telenet.be) |
06:21.32 | *** join/#openjtag aproemel (n=aproemel@www-cache.bocholt.fh-gelsenkirchen.de) |
06:29.44 | *** join/#openjtag rd_ (n=redragon@vnsecurity.net) |
10:36.24 | *** join/#openjtag aproemel (n=aproemel@www-cache.bocholt.fh-gelsenkirchen.de) |
10:37.27 | aproemel | hey vmaster :-) |
10:40.38 | vmaster | hey aproemel |
10:41.17 | aproemel | Do you think 2 weeks u-boot 5 weeks kernel to start init is to less? |
10:41.47 | vmaster | it could work - of course you're on a tight schedule, but you already know that i guess |
10:42.04 | vmaster | most of the porting is already done, and the board specific stuff is usually not that much |
10:42.30 | aproemel | yes, but i have to tell my boss in a few hours, how i plan to do my work |
10:42.44 | vmaster | especially since you don't need to support anything but memory + serial |
10:43.27 | aproemel | is it possible to boot a kernel like on a x86 arch ? |
10:43.34 | aproemel | so that the kernel boot itself ? |
10:45.09 | vmaster | you mean once you have a running kernel, you boot a new one? |
10:45.35 | vmaster | i've heard that this works on arm, too, but never tried it, and don't know what's necessary for it to work |
10:46.33 | aproemel | i mean, that i write the kernel at an address an boot it, like you write it at the start of a harddisk and then restart the x86 arch |
10:46.45 | aproemel | then the kernel boots itself, without any bootloader |
10:47.13 | vmaster | well, on x86 you have the BIOS, which does everything a bootloader does |
10:47.25 | aproemel | i know |
10:47.53 | vmaster | heh, yeah, then if you have a BIOS on your target, you can do without a bootloader ;) |
10:47.59 | aproemel | if i upload it with my loader thats inits ram, serial and the clocks, and jump to my kernel, do you think that'll work ? |
10:48.12 | vmaster | the kernel needs to be passed some arguments |
10:48.28 | vmaster | machine id, board id, and ATAG parameters with memory layout and cmdline |
10:48.46 | aproemel | what does the kernel without these informations? |
10:48.58 | vmaster | it fails booting |
10:49.07 | aproemel | does an output appear? |
10:49.17 | vmaster | no - at that time, there is /nothing/ |
10:49.31 | vmaster | you can add a "shim" that initializes this information |
10:49.43 | vmaster | people do that when their target has a bootloader that fails to pass the correct information |
10:50.16 | aproemel | :-( it was only an idea, to test my kernel build on my test board, without flash |
10:50.51 | vmaster | you could use the embest u-boot - you already have that working, don't you? |
10:51.50 | aproemel | mhh, i have to build the kernel new, cause board ID |
10:52.40 | vmaster | yeah, you can easily fake that in the kernel |
10:54.07 | aproemel | i'm currently run from one into another meeting :-( |
10:55.51 | aproemel | today 2 meetings, tomorrow 1, yesterday 1 |
10:56.09 | vmaster | ouch |
10:56.14 | aproemel | I spent more time to work for these meetings, that on my work :-( |
10:56.17 | vmaster | hard to get any work done this way |
10:56.19 | vmaster | yeah |
10:57.10 | aproemel | i'm working 7-15:30 without any break, then drive home, eat something and have to correct my written text of the morning ^^ |
10:57.52 | vmaster | heh, during the final phase of my diploma thesis i worked from 10:00 to 24:00+ ;) |
10:58.10 | aproemel | 10+ ^^ i get up at 5:30 every day |
10:58.17 | aproemel | drive 1hour |
10:58.25 | aproemel | and 1 hour back home |
10:59.27 | aproemel | i hope, that if i get my hardware, that it works correctly |
11:00.28 | aproemel | because i don't want to debug hardware a few weeks first, if i had to do so, everything isn't possible to get realized :-( |
11:05.40 | aproemel | in 45min i have to go to the meeting |
11:14.37 | rwhitby | a good arm shim can be found on marc singer's site |
11:15.27 | rwhitby | ftp://ftp.buici.com/pub/arm/arm-kernel-shim/ |
11:15.46 | aproemel | thnx rwhitby |
11:16.06 | rwhitby | (we use that for the ixp4xx boards that we support in nslu2-linux.org) |
11:16.18 | rwhitby | (where the vendor's bootloader is broken) |
13:23.28 | *** join/#openjtag rd_ (n=redragon@vnsecurity.net) |
13:35.58 | *** join/#openjtag bullet (n=bullet@171.212.203.62.cust.bluewin.ch) |
13:44.55 | *** join/#openjtag prpplague (n=dave@mail.americanmicrosystems.com) |
14:48.45 | *** join/#openjtag rd_ (n=redragon@vnsecurity.net) |
15:18.27 | *** join/#openjtag aproemel (n=aproemel@p508ABE16.dip0.t-ipconnect.de) |
15:36.04 | *** join/#openjtag wookey_ (i=wookey@217.147.92.90) |
16:25.03 | *** join/#openjtag AchiestDragon (n=david@whipy.demon.co.uk) |
19:04.32 | *** join/#openjtag vmaster_ (i=vmaster@p5B07D5A1.dip.t-dialin.net) |
19:31.26 | *** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox) |
19:50.40 | *** join/#openjtag rd_ (n=redragon@segfault.net) |
21:59.29 | *** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox) |
22:05.04 | *** join/#openjtag bullet (n=bullet@171.212.203.62.cust.bluewin.ch) |