• [00:05:59] * Crofton (n=balister@12.185.225.21) Quit ("Leaving")
  • [00:06:47] * jkridner (n=jason@c-76-31-18-64.hsd1.tx.comcast.net) has joined #beagle
  • [00:14:35] * bazbell (n=a0192809@nat/ti/x-37243295f2c2a193) Quit (Remote closed the connection)
  • [00:20:53] * NishanthM (n=Nishanth@cpe-24-175-68-203.tx.res.rr.com) has joined #beagle
  • [00:37:00] * bazbell (n=a0192809@nat/ti/x-9d4979a58ba44dd0) has joined #beagle
  • [01:01:53] * khasim (n=a0393720@192.163.20.231) has joined #beagle
  • [02:27:49] * khasim (n=a0393720@192.163.20.231) Quit (Remote closed the connection)
  • [06:01:57] * dirk2 (n=dirk@F329f.f.strato-dslnet.de) has joined #beagle
  • [06:21:03] * BThompson (n=BThompso@cpe-76-185-66-252.tx.res.rr.com) Quit ("Trillian (http://www.ceruleanstudios.com")
  • [08:40:24] * ldesnogu (n=ldesnogu@ven06-2-82-247-86-183.fbx.proxad.net) has joined #beagle
  • [09:00:49] * zodttd (n=recompil@user-142gtg7.cable.mindspring.com) Quit ()
  • [10:46:31] * koen (n=koen@s55917625.adsl.wanadoo.nl) Quit ("leaving")
  • [10:50:29] <jkridner> gm
  • [11:07:40] * Crofton (n=balister@86-42-199-64.b-ras1.cld.dublin.eircom.net) has joined #beagle
  • [11:11:36] <Crofton> gm
  • [11:15:17] * like2wise (n=likewise@82-171-51-231.ip.telfort.nl) has joined #beagle
  • [11:15:23] <Crofton> gm
  • [11:22:37] * like2wise (n=likewise@82-171-51-231.ip.telfort.nl) Quit ()
  • [11:28:18] * like2wise (n=likewise@82-171-51-231.ip.telfort.nl) has joined #beagle
  • [11:39:29] <jkridner> hi Crofton
  • [11:39:38] * horizon (i=horizon@141.30.223.123) Quit (Nick collision from services.)
  • [11:39:43] * horizon_ (i=horizon@141.30.223.123) has joined #beagle
  • [11:40:11] <jkridner> I do wish the PibbRelay would join more often. Some people do seem to like the live web chat.
  • [11:52:08] <jkridner> what is this stuff about bitbake not wanting to be run as root.
  • [11:52:10] <jkridner> ?
  • [11:52:24] <jkridner> you mean I actually have to create a user account? :)
  • [12:10:31] * like2wise (n=likewise@82-171-51-231.ip.telfort.nl) Quit (Read error: 104 (Connection reset by peer))
  • [12:11:10] * like2wise (n=likewise@82-171-51-231.ip.telfort.nl) has joined #beagle
  • [12:12:30] * like2wise (n=likewise@82-171-51-231.ip.telfort.nl) Quit (Client Quit)
  • [12:12:45] * jkridner|work (n=a0321898@nat/ti/x-f755ed875c1b2847) has joined #beagle
  • [12:23:13] <dirk2> altex5, jkridner|work: Nice blogging http://beagleboard.blogspot.com/ ;)
  • [12:23:30] <jkridner> dirk2: thanks for giving the content!
  • [12:23:48] <dirk2> Thanks for improving it!
  • [12:24:23] <jkridner> what I found was that the blog entries could be saved as draft and then other bloggers could come and edit it later.
  • [12:24:56] <dirk2> ah! Good option for altex5...
  • [12:24:59] <jkridner> if you want to continue to contribute, the e-mails are fine, but you could also post a draft on the blog directly, then I could edit for American English grammar and style.
  • [12:25:37] <jkridner> of course, it would also be nice to have a German blog!
  • [12:26:05] <jkridner> If you give me the RSS feed, I can aggregate it into the feed from http://beagleboard.org.
  • [12:26:19] <jkridner> I've actually set it up to use Yahoo pipes.
  • [12:26:45] <jkridner> I pass it through Google Reader so that I can approve all items before they are put onto the main RSS feed.
  • [12:27:29] <jkridner> anyway, thanks a lot for the ideas and help.
  • [12:27:35] <jkridner> they were very good.
  • [12:28:06] <dirk2> English blogs are more universal ;) Most people can read english blogs, but not everybody can read German
  • [12:28:40] <dirk2> In Android wiki there is a taiwanese site with proposal to feed it through google translator ;)
  • [12:29:29] <dirk2> jkridner: I looked for TWL4030 data sheet. It isn't available public?
  • [12:29:38] <jkridner> I need to run Google translator on the Chinese forum posts on Beagle.
  • [12:29:48] <jkridner> no, I don't think it is public.
  • [12:30:16] <jkridner> there will be a fully compatible device released to the public. I need to look up the part number.
  • [12:30:36] <dirk2> :( Then we need an "insider" demistifying this TWL clock discussion
  • [12:30:40] <jkridner> It would be a drop-in replacement if you wanted to make your own Beagle.
  • [12:31:07] <jkridner> I guess I didn't follow the e-mail traffic well. I thought the mystery was unraveling.
  • [12:31:54] <dirk2> Yes and no ;)
  • [12:32:40] <dirk2> Tony thinks that I2C/TWL issue on beagle comes from touching TWL with wrong clock before doing correct clock configuration in kernel
  • [12:33:11] <dirk2> And our beagle uboot *does* touch TWL prior to kernel
  • [12:33:28] <jkridner> right, so I thought his explanation made sense.
  • [12:34:04] <dirk2> Yes, but how to figure out how to deal with TWL in uboot correctly without manual?
  • [12:34:34] <jkridner> ugh, 56 mails open right now.
  • [12:35:05] <jkridner> I'll look for the info/ETA on the manual.
  • [12:36:38] <dirk2> Or maybe an "insider" can give a hint "try this or that value" in uboot for TWL? If this works, it would be sufficient without manual ;)
  • [12:37:11] <dirk2> I think NishantM is currently doing a lot of uboot work.
  • [12:38:25] <jkridner> so, do you have a guess for why the git tree fails but the .22 build works?
  • [12:39:05] <jkridner> btw, I don't think anyone ever submitted the Beagle u-boot patches beyond the beagle mailing list, did they?
  • [12:39:16] <dirk2> No.
  • [12:39:20] <jkridner> I think we all gave the feedback, but I never...
  • [12:39:21] <jkridner> right.
  • [12:39:59] <dirk2> patches: Yes, they need a major rework for upstream sending...
  • [12:40:40] <dirk2> patches: I'm not sure if this rework still make sense, or if the work wouldn't better be spent to help NishanthM with clean uboot v2
  • [12:41:53] <dirk2> why .22 kernel works: I don't know. I lost the overview which combinations of MLO, uboot and kernel work and which with which symptoms not :(
  • [12:42:17] <dirk2> Actually, I think koen should have the best overview
  • [12:43:27] <jkridner> patches: I worry that much functionality of v2 is still a way off. I believe Beagle developers need the USBTTY+DFU support in u-boot soon (to avoid the serial cable and need for SD card).
  • [12:44:51] <jkridner> on latest kernel vs .22: I also have not kept track. I'm consistently on .22 right now playing with the USB EHCI stuff. (When I'm not distracted with demos, presentations, and general unproductiveness.)
  • [12:45:01] <jkridner> (blog posts ;) )
  • [12:45:30] <jkridner> (ok, so those blog posts didn't take much time thanks to you.)
  • [12:45:41] <dirk2> ;)
  • [12:46:09] <dirk2> kernel: You run .22 with 500 MHz MLO, uboot and L2 on without issues?
  • [12:48:27] <jkridner> yes.
  • [12:48:41] <jkridner> I run something very close to the binaries I provided.
  • [12:49:26] <jkridner> although I did switch to an older MLO/uboot recently to address issues when programming the on-board flash, but I'm not using it all the time.
  • [12:50:29] <jkridner> if you start to program the on-board flash, but don't give a completely valid boot image, the published MLO can give you an error reading the flash and hang.
  • [12:50:54] <dirk2> kernel: okay, good to know. Maybe we should discuss with koen a "these binaries are working in this combination" matrix/table at wiki page
  • [12:50:55] <jkridner> it will print something about an 8-bit vs. 16-bit error.
  • [12:51:41] <jkridner> that could be very helpful, as long as the list is kept reasonably short.
  • [12:52:02] <jkridner> something that points to source and a particular build.
  • [12:52:10] <dirk2> That depends on the number of binary images ;))
  • [12:52:32] <dirk2> points: Yes
  • [12:52:45] <jkridner> I think we can find someone inside TI to test (give thumbs-up or down) some time next week (if it doesn't happen elsewhere).
  • [12:53:12] <jkridner> right, we should just point to one set of binary builds per set of sources (preferably)..
  • [12:53:31] <jkridner> and only have a couple points on the git tree (need to include identifiers).
  • [12:53:49] <jkridner> I can host images or koen or xxx.
  • [12:54:02] <jkridner> would that help things get debugged faster?
  • [12:54:47] <jkridner> it'd always be nicer for the git tip to work, but we should always try to know the latest that did work.
  • [12:55:05] <jkridner> you know, it should probably be a matrix of functionality. :-|
  • [12:55:14] <dirk2> work: Yes. As today with OMAP git ;)
  • [12:55:18] <jkridner> USB EHCI, USB OTG, MMC/SD, etc.
  • [12:55:43] <dirk2> I2C, L2 cache, 500MHz etc.
  • [12:56:35] <jkridner> eventually, I'd expect us to have a bit of a mini test-farm that can always probe the git status, but I'm many weeks from that.
  • [12:56:49] <jkridner> I2C, L2, 500MHz, etc., right.
  • [12:57:34] <jkridner> We can leave off areas not yet covered well, such as 600MHz, cpufreq, etc., but they will come later.
  • [12:58:04] <dirk2> Yes.
  • [13:00:28] <jkridner> btw, I have my first 'bitbake nano' running.
  • [13:01:09] <dirk2> Don't tell it koen, but never tried it...
  • [13:01:24] <jkridner> I had a few hiccups getting it started. It seems the Gentoo people don't use 'bitbake', but it is very easy to add to Gentoo.
  • [13:01:38] <jkridner> :O
  • [13:01:42] * ali_as_ (n=as@ambix.plus.com) has joined #beagle
  • [13:02:20] <dirk2> ali_as: Hi
  • [13:03:04] <jkridner> I'm not sure I like the idea of learning monotone. I'm still trying to learn git.
  • [13:04:08] <dirk2> I can: cg_upate (not supported any more), git status and have a txt telling me how to use git-send-mail
  • [13:04:26] <dirk2> And today I used git checkout after reading the manual
  • [13:05:39] <sakoman> jkridner: the oe guys are considering switching to git
  • [13:06:07] <jkridner> I get frustrated by tool writers who expect everyone to invest the amount of time they do in learning the tool.
  • [13:06:16] <jkridner> sakoman: that would be nice.
  • [13:07:00] <jkridner> I just 'guessed' that 'git checkout' would take that big hash sum as an argument to go to that point in the revision tree.
  • [13:07:03] <jkridner> seems to work.
  • [13:07:22] <dirk2> jkridner: Correct
  • [13:07:23] <jkridner> haven't seen where that is documented--just expected it to behave that way and it did.
  • [13:07:49] <sakoman> no kidding. I'm busy learning git too. Got as far as setting up a public git where I test stuff before sending patches upstream.
  • [13:07:52] <jkridner> bad news is that I could be generating side effects that I don't know about because I haven't read the right docs.
  • [13:07:59] <sakoman> http://www.sakoman.net/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=summary
  • [13:08:45] <jkridner> looks like you are following closely (recent updates)
  • [13:08:46] <dirk2> sakoman: Does the bootloader (uboot?) on your OMAP3 evm touch TWL4030?
  • [13:09:11] <jkridner> I hadn't seen that Balbi post yet.
  • [13:09:17] <sakoman> I have no idea! Haven't dived into the u-boot source yet
  • [13:09:36] <dirk2> sakoman: How do you boot? Do you use MMC?
  • [13:09:47] <sakoman> I boot from onenand
  • [13:10:00] <sakoman> so that might make a big difference
  • [13:10:05] <jkridner> darn, it is just an MUSB patch, not ECHI.
  • [13:10:08] * like2wise (n=likewise@82-171-51-231.ip.telfort.nl) has joined #beagle
  • [13:10:47] <dirk2> sakoman: Is the OMAP3 EVM uboot code you use available somewhere to grep for "twl"?
  • [13:11:24] <sakoman> yeah, I think I have it here somewhere. Let me check
  • [13:11:58] <sakoman> I seem to recall that TI might have post it publicly recently
  • [13:12:24] <sakoman> It is also on the Mistral site -- but not sure if it is the same
  • [13:13:35] <dirk2> http://focus.ti.com/general/docs/wtbu/wtbusplashcontent.tsp?templateId=6123&contentId=4750#omap3530 ?
  • [13:14:06] <ldesnogu> http://focus.ti.com/general/docs/wtbu/wtbusplashcontent.tsp?templateId=6123&contentId=4750
  • [13:14:17] <ldesnogu> this one has link to all :)
  • [13:14:24] <jkridner> :)
  • [13:16:13] * ldesnogu hides, ashamed
  • [13:16:14] <jkridner> sakoman: I know your tree isn't meant for public consumption/contribution, but you do know about 'cloneurl' files, right? :)
  • [13:16:36] <sakoman> nope
  • [13:16:37] * jkridner is happy that people can get the code now without the EVM registration.
  • [13:17:33] <jkridner> I don't know if there are tools to manage these magic files that sit in the repository, but gitweb uses 'cloneurl' to display the download url.
  • [13:20:35] <jkridner> I'm looking for examples, but I don't know where I found them before.
  • [13:20:52] <jkridner> you can look at http://www.beagleboard.org/beagleboard.org.git/
  • [13:21:11] * ali_as (n=as@ambix.plus.com) Quit (Read error: 110 (Connection timed out))
  • [13:21:35] <jkridner> just adds the URL section on http://www.beagleboard.org/gitweb/?p=beagleboard.org.git;a=summary
  • [13:22:00] <sakoman> Ah, I see
  • [13:23:39] <sakoman> Yeah, maybe I *don't* want that :-)
  • [13:24:10] <jkridner> hehe
  • [13:25:32] <sakoman> dirk2: a grep of twl4030 in my u-boot sources yeilds nothing
  • [13:26:06] <dirk2> Thanks! This could be one hint, why it behaves different on EVM and Beagle!
  • [13:27:01] <dirk2> My theory based on Tony's hint actually is that Beagle uboot touches TWL "in the wrong way" before kernel can configure TWL correctly.
  • [13:28:51] <sakoman> jkridner: still trying to figure out the best way of organizing things so I can stay synced with linux-omap, make local changes & pull from my oe recipe, generate patches, and merge after patch acceptance.
  • [13:29:12] <sakoman> And not lose my mind in the process
  • [13:29:19] <jkridner> I wish I had good hints for you.
  • [13:29:27] <sakoman> Me too :-)
  • [13:30:10] <sakoman> I'm muddling along, I'm sure it will become obvious after all this becomes more familiar
  • [13:30:12] <jkridner> We were looking at doing a downstream git for Beagle to stage things for Tony, but it seems easier for now to just use Tony's git.
  • [13:31:29] <dirk2> I use Tony's git and quilt. Before I cg-update from Tony, I quilt pop everything, then cg-update, then remove stuff from series file what is pushed alreay, and quilt push
  • [13:31:33] <jkridner> well, your muddling is working pretty well, at least for the EVM. (Beagle coming soon(TM))
  • [13:31:41] <sakoman> That's what I started doing, but it becomes really complicated when you've got a bunch of patches submitted but not accepted, some tested but not submitted, and others in various stages of test and development
  • [13:31:57] <dirk2> Yes
  • [13:32:36] <sakoman> I got tired of keeping patches in oe and moving things around with submission/acceptance
  • [13:33:03] <sakoman> So now I'm just using my got for the oe recipe and doing merges after patch acceptance
  • [13:33:09] <sakoman> my git
  • [13:33:18] <sakoman> jeeze, need more coffee
  • [13:34:02] <dirk2> jkridner: Do you like to paste .22 drivers/i2c/chips/twl4030-core.c to http://rafb.net/paste/
  • [13:34:12] <dirk2> ?
  • [13:34:48] <jkridner> k. could be several minutes.
  • [13:35:08] <dirk2> Thanks if I'm away then!
  • [13:35:32] <dirk2> Just post the link, I'm reading the logs
  • [13:40:22] * dirk2 (n=dirk@F329f.f.strato-dslnet.de) has left #beagle
  • [13:58:28] <jkridner> dirk2: http://rafb.net/p/CIJMmF95.html
  • [14:19:29] <bazbell> Those asking about the TWL4030, dirk2, who just left, posted the twl4030_mmc_config() routine from u-boot. In order to boot from an external SDCard, the TWL4030 must be configured to output 3.0V on the rail to the card cage and to MMC1 interface. The default voltage is 1.85V. The ic2_write(0x4B, 0x85, 1, &data, 1) where data = 0x2 is what does this.
  • [14:20:11] * koen (n=koen@s55917625.adsl.wanadoo.nl) has joined #beagle
  • [14:25:22] <koen> good morning all
  • [14:25:29] <ldesnogu> hi koen
  • [14:28:20] <koen> jkridner|work: would the twl5030 be the "public" part?
  • [14:28:22] <koen> hey ldesnogu
  • [14:30:44] <ldesnogu> twl4030's codename is Triton 2, that reminds me of something back when I worked at TI :)
  • [14:31:34] <koen> neptune?
  • [14:31:46] <ldesnogu> that's strand twl4030 is associated to OMAP2, while 5030 is associated to OMAP3
  • [14:31:54] <ldesnogu> s/strand/strange/
  • [14:32:33] <ldesnogu> koen: no, I think some people in TI France were working on sth named Triton a few years ago
  • [14:32:46] <koen> ah
  • [14:32:47] <ldesnogu> perhaps that part was designed in France
  • [14:32:58] <ldesnogu> which could explain... :D
  • [14:33:14] <koen> My beagle board does have a physical chip with "TWL4030" printed on it :)
  • [14:33:42] <ldesnogu> well if you google twl4030 and twl5030 you will see what I mean :)
  • [14:34:28] <koen> It explains why I get:
  • [14:34:47] <koen> triton2 power button driver initialized
  • [14:34:47] <koen> input: triton2-pwrbutton as /class/input/input0
  • [14:34:50] <koen> in my boot log :)
  • [14:34:56] <ldesnogu> probably :)
  • [14:35:25] <bazbell> It would be wonderful if we did not put codenames into code.
  • [14:35:30] <ldesnogu> I am wondering if internal names can be put public :)
  • [14:35:39] <ldesnogu> s/put/made/
  • [14:35:42] * Crofton (n=balister@86-42-199-64.b-ras1.cld.dublin.eircom.net) Quit (Read error: 110 (Connection timed out))
  • [14:36:04] <bazbell> Part numbers are unique, codenames get reused.
  • [14:36:09] <ldesnogu> it looks like arm does: cortex-a8 was named Tiger
  • [14:36:17] * ldesnogu looks for cortex-a9
  • [14:36:31] <ldesnogu> it's public too
  • [14:36:33] <ldesnogu> Falcon :)
  • [14:37:23] <koen> is there already a CPU that uses the cortex-a9 on the market
  • [14:37:24] <koen> ?
  • [14:37:38] <ldesnogu> not yet
  • [14:38:45] <ldesnogu> but there are some already known licensees
  • [14:39:07] <ldesnogu> TI being one of them ;)
  • [14:40:09] * koen discovers http://linux.omap.com/pub/kernel/3430sdp/patches-applicable-over-linux-omap-2.6.git/audio_34xx_support_20071220.patch
  • [14:41:00] <ldesnogu> hum isn't that also the date at which TI built its .22 kernel?
  • [14:41:19] * koen has no idea
  • [14:41:38] <koen> I don't see much in developing for .22
  • [14:41:48] <ldesnogu> I agree
  • [14:41:58] <koen> especially seeing how TI/mistral/whoever added the board support
  • [14:42:07] <koen> #ifdef spaghetti code
  • [14:42:38] <ldesnogu> someone has to push that to "official"??? linux OMAP
  • [14:42:48] <koen> heh
  • [14:43:03] <koen> starting from scratch is less work and has more change being accepted
  • [14:43:27] <koen> especially since most beagle stuff can de copied either from 3430sdp or omap3evm
  • [14:43:38] <ldesnogu> but isn't using what TI did as a basis the way to go, especially when some docs are not public?
  • [14:44:21] <koen> you first have to decode what the code does
  • [14:44:42] <ldesnogu> I have that feeling when I look at standard kernel
  • [14:44:46] <ldesnogu> is that worse?
  • [14:45:05] <koen> like:
  • [14:45:06] <koen> omap_writel(0x001C001C, 0x480021C4);
  • [14:45:14] <koen> omap_set_gpio_dataout(170,1);
  • [14:45:33] <ldesnogu> that's unavoidable if associated document is not public :(
  • [14:45:45] * NishanthM (n=Nishanth@cpe-24-175-68-203.tx.res.rr.com) Quit (Read error: 110 (Connection timed out))
  • [14:46:13] <koen> does it kill people to do #define DVI_ENABLE 170 or #define TFP_MAGIC_ADDRESS 0x001c001c ?
  • [14:46:41] <ldesnogu> it does if it gives you some reg name that is not public
  • [14:47:36] <koen> ldesnogu: http://dominion.thruhere.net/koen/cms/fun-with-vendor-patches
  • [14:47:50] <koen> vendors trying to annoy other vendors in patches
  • [14:48:18] <ldesnogu> that's really bad indeed
  • [14:49:26] <ldesnogu> but I don't think it's a similar case here :)
  • [14:49:46] <koen> no, but I like to show that case :)
  • [14:49:50] <ldesnogu> BTW, what is TFP?
  • [14:50:16] <ldesnogu> it looks like it's not part of omap35 memory map
  • [14:50:20] <bazbell> Documentation for address 0x480021C4 is located at http://focus.ti.com/docs/prod/folders/print/omap3530.html in the TRM document SPRUF98.
  • [14:50:52] <ldesnogu> you mean this is writel(data, address) ? now that hurts :)
  • [14:51:51] <bazbell> Based on the data and the fact that 0x001C001C would be the somewhere in the middle of the GPMC address range.
  • [14:52:02] <koen> I know why vendor patches are so "bad", they get written under huge time pressure
  • [14:52:10] <bazbell> Yes, it is (data, address)
  • [14:52:37] * ldesnogu should erase his 20 years old BASIC poke memories
  • [14:54:36] <koen> 3.4k pages
  • [14:55:00] <bazbell> PDF search is a good thing
  • [14:55:04] <ldesnogu> well I'm happy then that ???0x001c001c was not defined as ??????TFP_MAGIC_ADDRESS, it would be very bad :)
  • [14:55:11] <koen> :D
  • [14:56:03] <bazbell> ldesnogu: Where do you find TFP?
  • [14:56:20] <ldesnogu> koen was playing tricks on me :)
  • [14:56:25] <koen> yeah
  • [14:56:31] <ldesnogu> ???(04:41:51 PM) koen: does it kill people to do #define DVI_ENABLE 170 or #define TFP_MAGIC_ADDRESS 0x001c001c ?
  • [14:56:36] <koen> the tfp isn't memorymapped
  • [14:57:02] * JoeBorn_ (n=jborn@cpe-66-1-5-91.il.sprintbbd.net) has joined #beagle
  • [14:57:24] <koen> only 24 pixel data lines, hsync, vsync and power are connected
  • [14:57:26] <koen> and a clock
  • [15:02:26] <koen> ah, the maskrom also touches twl
  • [15:03:06] <bazbell> koen: I'm not sure I understand what you are asking wrt the display subsystem interface.
  • [15:03:37] <koen> bazbell: I was just making observations that it's *I$@#*(@#*$(@# hard to get answers out of the .22 code
  • [15:03:45] <bazbell> okay
  • [15:04:50] <koen> things like "foo = 1024; /* set to 320 */"
  • [15:05:31] <ldesnogu> you forgot to say what unit is used in your comment, kHz or ns? :)
  • [15:06:05] <koen> in this case it was "pixels" (xres)
  • [15:06:37] <koen> but foo was something like H4_LCD_FOO
  • [15:06:58] <ldesnogu> which is easier to read
  • [15:07:29] <koen> beagle support in .22 is a combination of sdp,h4 and problably more boards
  • [15:07:37] <koen> which is great, but very confusing
  • [15:07:54] <koen> (I'm documention my DVI odessy, not complaining)
  • [15:08:06] <ldesnogu> so according to what Richard said, one can't assume anything for values after the mask ROM... which is not documented :(
  • [15:09:23] <koen> we could dump regisrers after a .22 boot, right?
  • [15:09:33] <ldesnogu> are all regs R/W?
  • [15:09:47] <bazbell> ldesnogu: Agree that is a pain. The ROM code can go through many different legs which may affect how it configures the device.
  • [15:09:56] <bazbell> The registers are certainly readable.
  • [15:11:31] <ldesnogu> that's good to know, I have seen devices where writing does sth while reading does sth else :)
  • [15:13:53] * jkridner is off to play hockey
  • [15:21:44] <koen> ldesnogu: or that you need *2* reads to get the correct value
  • [15:21:48] <koen> (intel xscales)
  • [15:22:46] * JoeBorn_ is now known as JoeBorn
  • [15:22:57] <ldesnogu> xscales are that buggy or is it by design?
  • [15:32:29] * like2wise (n=likewise@82-171-51-231.ip.telfort.nl) Quit ()
  • [15:34:13] <koen> buggy
  • [15:55:49] * Crofton (n=balister@86-42-199-64.b-ras1.cld.dublin.eircom.net) has joined #beagle
  • [16:00:08] * like2wise (n=likewise@82-171-51-231.ip.telfort.nl) has joined #beagle
  • [16:00:28] * BThompson (n=BThompso@cpe-76-185-66-252.tx.res.rr.com) has joined #beagle
  • [16:06:01] * NishanthM (n=Nishanth@cpe-24-175-68-203.tx.res.rr.com) has joined #beagle
  • [16:08:00] <koen> rtc patch accepted, hopefully it will enter git on monday
  • [16:09:11] <koen> like2wise: enjoying the mbp?
  • [16:26:16] <like2wise> koen: mbp?
  • [16:27:19] <like2wise> koen: uh, YES! :-)
  • [16:28:29] <like2wise> koen: but design flaw #1 (screen cannot tilt backwards enough) bites me a biy
  • [16:28:31] <like2wise> bit
  • [16:32:13] <koen> I still like the 12" powerbook better
  • [16:32:50] <koen> like2wise: actually design flaw #1 is the 6bit panel
  • [16:33:10] <like2wise> ouch, I have a 6 bit panel? :-/
  • [16:33:18] <koen> most likely
  • [16:34:10] <koen> I was blaming my camera (the 20D has a known banding problem), but the banding also appeared in generated content
  • [16:34:50] <koen> like2wise: you can check with http://peewaiweb.free.fr/
  • [16:37:04] * NishanthM (n=Nishanth@cpe-24-175-68-203.tx.res.rr.com) Quit (Read error: 110 (Connection timed out))
  • [16:37:12] * koen hugs his stationary tft
  • [16:37:13] * NishanthM (n=Nishanth@cpe-24-175-68-203.tx.res.rr.com) has joined #beagle
  • [16:37:34] <koen> with 2x dvi so I can attach the mac and beagle at the same time :)
  • [16:45:57] <like2wise> yes, I have got the worst of the displays, googling tells me
  • [16:46:10] <koen> welcome to the club :(
  • [16:46:21] <koen> sorry to rain on your parade
  • [16:46:27] <like2wise> :-)
  • [16:46:30] <like2wise> np,
  • [16:46:38] <like2wise> the dollar was extra low :-)
  • [16:46:52] <like2wise> bbq time - shower first - cya!
  • [16:46:52] <koen> it's like 60 cents nowadays
  • [16:46:56] <koen> :)
  • [16:47:01] <koen> enjoy the bbq
  • [16:47:07] <like2wise> tnx
  • [16:48:16] <koen> time to move to the balcony with some wheat beer
  • [16:58:42] * like2wise is now known as like|away
  • [16:58:52] * like|away (n=likewise@82-171-51-231.ip.telfort.nl) Quit ()
  • [17:15:00] * NishanthM (n=Nishanth@cpe-24-175-68-203.tx.res.rr.com) Quit (Read error: 110 (Connection timed out))
  • [17:15:25] * NishanthM (n=Nishanth@cpe-24-175-68-203.tx.res.rr.com) has joined #beagle
  • [17:48:07] * NishanthM (n=Nishanth@cpe-24-175-68-203.tx.res.rr.com) Quit (Read error: 110 (Connection timed out))
  • [17:48:31] * NishanthM (n=Nishanth@cpe-24-175-68-203.tx.res.rr.com) has joined #beagle
  • [17:55:32] * bazbel1 (n=a0192809@nat/ti/x-4f9b08b4f699e7ac) has joined #beagle
  • [17:59:26] * bazbell (n=a0192809@nat/ti/x-9d4979a58ba44dd0) Quit (Remote closed the connection)
  • [18:02:11] * bazbel1 (n=a0192809@nat/ti/x-4f9b08b4f699e7ac) Quit (Remote closed the connection)
  • [18:18:31] * NishanthM (n=Nishanth@cpe-24-175-68-203.tx.res.rr.com) Quit (Read error: 110 (Connection timed out))
  • [18:18:44] * NishanthM (n=Nishanth@cpe-24-175-68-203.tx.res.rr.com) has joined #beagle
  • [18:51:59] * NishanthM (n=Nishanth@cpe-24-175-68-203.tx.res.rr.com) Quit (Read error: 110 (Connection timed out))
  • [18:54:07] * bazbell (n=a0192809@adsl-99-142-64-94.dsl.emhril.sbcglobal.net) has joined #beagle
  • [19:25:26] * NishanthM (n=Nishanth@cpe-24-175-68-203.tx.res.rr.com) has joined #beagle
  • [21:22:11] * koen hopes the twl issues will get resolved soon now we seem to know the cause
  • [21:48:05] * like2wise (n=likewise@82-171-51-231.ip.telfort.nl) has joined #beagle
  • [22:04:15] <like2wise> koen: yay, according to this test (http://www.leppik.net/david/blog/?p=58) it's a 24-bit screen after all.
  • [22:11:46] <like2wise> or at least its temporally corrected or whatever
  • [22:22:23] <jkridner> koen: I attempted 'bitbake task-base' and it fails on git-native.
  • [22:22:44] <jkridner> is that expected?
  • [22:25:08] <like2wise> jkridner: what kind of error?
  • [22:25:28] <jkridner> ERROR: Task 1015 (/home/angstrom/stuff/org.openembedded.dev/packages/git/git-native_1.5.3.bb, do_compile) failed
  • [22:26:08] <like2wise> jkridner: no that's not expected (if I may speak for koen here).
  • [22:26:51] <jkridner> NOTE: Tasks Summary: Attempted 325 tasks of which 269 didn't need to be rerun and 1 failed.
  • [22:26:58] <like2wise> jkridner: is this your first build or has this worked before? If it worked, did you recently upgrade OE? (The .dev. branch is actively worked on).
  • [22:27:01] <jkridner> so, it got some of the way there.
  • [22:27:09] <jkridner> this is my first use of OE.
  • [22:27:19] <like2wise> jkridner: on which host machine and os?
  • [22:27:45] <jkridner> I used Gentoo to cross-compile to ARM before, but I was having problems getting the X11 stuff done.
  • [22:27:48] <jkridner> I run Gentoo.
  • [22:28:04] <jkridner> Portage 2.1.4.4 (default-linux/x86/2007.0, gcc-4.1.1, glibc-2.5-r0, 2.6.16-xenU i686)
  • [22:28:22] <like2wise> jkridner: OE expect a small set of host tools to be present, and builds the rest itself. See http://oe.linuxtogo.org/wiki/OEandYourDistro
  • [22:28:33] <like2wise> s/expect/expects/
  • [22:28:36] <jkridner> Linux domU-12-31-38-00-9C-98 2.6.16-xenU #1 SMP Mon May 28 03:41:49 SAST 2007 i686 Dual-Core AMD Opteron(tm) Processor 2218 HE AuthenticAMD GNU/Linux
  • [22:29:06] <jkridner> I completed the setup per Gentoo.
  • [22:29:31] <jkridner> bitbake required me to make an ebuild as I needed a newer version of bitbake for the database.
  • [22:29:45] <like2wise> ah.
  • [22:30:05] <jkridner> openjade gave me some headaches as well, but I get them confused with the openjade headaches I had with my Mac.
  • [22:30:13] <like2wise> probably just un-emerge bitbake and checkout a local copy of a very recent bitbake is better
  • [22:30:32] <like2wise> .dev. works against bitbake-1.8.10 recent builds only.
  • [22:30:42] <jkridner> I have 1.8.10
  • [22:30:58] * Crofton (n=balister@86-42-199-64.b-ras1.cld.dublin.eircom.net) Quit (Connection timed out)
  • [22:31:44] <jkridner> the ebuild I made didn't apply any patches.
  • [22:31:50] <like2wise> jkridner: rev 1060+ or so?
  • [22:32:07] <jkridner> how do I check? -s gave me a long list.
  • [22:33:28] * Crofton (n=balister@86-42-199-64.b-ras1.cld.dublin.eircom.net) has joined #beagle
  • [22:33:33] <like2wise> most of the .dev guy just checkout the latest bitbake in their projects.:
  • [22:33:34] <like2wise> svn checkout svn://svn.berlios.de/bitbake/tags/`svn ls svn://svn.berlios.de/bitbake/tags/ | grep '1.8.10'` bitbake
  • [22:33:50] <jkridner> BitBake Build Tool Core version 1.8.10, bitbake version 1.8.10
  • [22:34:24] * jkridner needs to leave for a dinner out.
  • [22:34:37] <jkridner> thanks like2wise. I'll try again later.
  • [22:34:51] <like2wise> jkridner: I would check with the latest bitbake
  • [22:34:56] <like2wise> jkridner: i'm off to bed.
  • [22:35:09] <like2wise> have a nice dinner out, and cya
  • [22:35:18] * like2wise (n=likewise@82-171-51-231.ip.telfort.nl) Quit ()
  • [22:54:46] <ldesnogu> gn all
  • [22:54:48] * ldesnogu (n=ldesnogu@ven06-2-82-247-86-183.fbx.proxad.net) has left #beagle
  • [23:00:09] * bazbell (n=a0192809@adsl-99-142-64-94.dsl.emhril.sbcglobal.net) Quit (Read error: 110 (Connection timed out))