2012-01-11 00:05 <wpwrak> hehe :)
2012-01-11 00:06 <wpwrak> (build from source) i'll have to add some things for boom interaction anyway
2012-01-11 00:06 <wpwrak> (upstream) don't you as the author of those patches want to do it yourself ?
2012-01-11 00:11 <wolfspraul> I am overloaded
2012-01-11 00:11 <wolfspraul> no news in ... months
2012-01-11 00:12 <wolfspraul> plus I think my main work nowadays is simply to find money
2012-01-11 00:12 <wolfspraul> as much as I like coding
2012-01-11 00:12 <wolfspraul> can't do it
2012-01-11 00:13 <wpwrak> i think the news concept has failed. at least the news-with-wolfgang-as-editor. pity. but maybe someone else will step up at some point in time.
2012-01-11 00:14 <wpwrak> (find money) yes !! :)
2012-01-11 00:14 <wolfspraul> we don't have many readers anyway
2012-01-11 00:14 <wolfspraul> so the reason is more for archival purposes, and I do continue to connect those links
2012-01-11 00:14 <wolfspraul> of course the intervals are not good
2012-01-11 00:14 <wolfspraul> one by one
2012-01-11 00:15 <wpwrak> (coding) with a little luck, upstreaming shouldn't be too dreadful. and probably easier to do it yourself than explain to xiangfu why exactly you've done what
2012-01-11 00:15 <wolfspraul> possible, I will see
2012-01-11 00:15 <wolfspraul> no worries we will try what works best
2012-01-11 00:15 <wolfspraul> no dogma
2012-01-11 00:15 <wolfspraul> but if xiangfu can help me, great
2012-01-11 00:15 <wolfspraul> I don't want another up-leveling in 2013
2012-01-11 00:16 <wolfspraul> I have no idea how 2011 disappeared so fast...
2012-01-11 00:17 <wpwrak> ;-))
2012-01-11 00:40 cladamw [cladamw!~adamwang@host-222.80-43-115.dynamic.totalbb.net.tw] has joined #qi-hardware
2012-01-11 01:25 xiangfu [xiangfu!~xiangfu@fidelio.qi-hardware.com] has joined #qi-hardware
2012-01-11 02:54 * pabs3 wants an open hardware, firmware version of the Crypto Stick
2012-01-11 03:01 rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware
2012-01-11 03:18 cladamw [cladamw!~Adam@host-222.80-43-115.dynamic.totalbb.net.tw] has joined #qi-hardware
2012-01-11 03:23 * kristianpaul Dormido
2012-01-11 04:48 paroneayea [paroneayea!~user@fsf/member/paroneayea] has joined #qi-hardware
2012-01-11 05:09 paroneayea [paroneayea!~user@fsf/member/paroneayea] has joined #qi-hardware
2012-01-11 05:16 paroneayea [paroneayea!~user@fsf/member/paroneayea] has joined #qi-hardware
2012-01-11 05:28 cladamw [cladamw!~Adam@host-222.80-43-115.dynamic.totalbb.net.tw] has joined #qi-hardware
2012-01-11 05:48 Jay7 [Jay7!jay@128-73-56-213.broadband.corbina.ru] has joined #qi-hardware
2012-01-11 06:26 DocScrutinizer [DocScrutinizer!~halley@openmoko/engineers/joerg] has joined #qi-hardware
2012-01-11 07:09 cladamw [cladamw!~Adam@host-222.80-43-115.dynamic.totalbb.net.tw] has joined #qi-hardware
2012-01-11 07:17 jekhor [jekhor!~jek@vulture2-nat-41.telecom.by] has joined #qi-hardware
2012-01-11 07:32 stefan_schmidt [stefan_schmidt!~stefan@guest232.ibr.cs.tu-bs.de] has joined #qi-hardware
2012-01-11 07:59 <wolfspraul> pabs3: are you saying the crypto stick is not open?
2012-01-11 08:01 <pabs3> wolfspraul: not according to their intro page: "integrated (proprietary) smart card": http://www.crypto-stick.com/en/introduction
2012-01-11 08:02 <wolfspraul> hmm, ok
2012-01-11 08:02 <wolfspraul> need to find out more first
2012-01-11 08:02 <wolfspraul> but I doubt it's proprietary because that's their business model
2012-01-11 08:05 <viric> larsc: ah the patch... at the evening. I've that in my home computer
2012-01-11 08:20 <pabs3> wolfspraul: if they're assembling off-the-shelf components (like that ATMEL or the uSD card), probably some of those are proprietary in some way: http://www.crypto-stick.com/2011/crypto-stick-2-beta-boards-arrived
2012-01-11 08:22 <wolfspraul> sure, unless I see them actively closing up something somewhere, I'm not worried
2012-01-11 08:22 <wolfspraul> and I think they are doing a serious and good project, but slowly we will learn more about it
2012-01-11 08:42 DocScrutinizer [DocScrutinizer!~halley@openmoko/engineers/joerg] has joined #qi-hardware
2012-01-11 08:59 Ayla [Ayla!~paul@87.169.26.93.rev.sfr.net] has joined #qi-hardware
2012-01-11 09:09 <DocScrutinizer> stay tuned for c't testing the crypto-stick... ?
2012-01-11 09:23 jekhor [jekhor!~jek@mx2.promwad.com] has joined #qi-hardware
2012-01-11 09:46 <wolfspraul> DocScrutinizer: thanks a lot for helping out with the J3 audio expansion thing!
2012-01-11 09:46 <DocScrutinizer51> yw
2012-01-11 09:47 <wolfspraul> we start to polish the details a bit :-)
2012-01-11 09:47 <DocScrutinizer51> I strongly prefer helping during design phase rather than later fixing hw bugs
2012-01-11 09:48 <wolfspraul> well in that case it's just about reducing that big header to something more thoughtful
2012-01-11 09:48 <wolfspraul> which I'm sure we now have, thanks to your help too
2012-01-11 09:48 <DocScrutinizer51> and I'm regularly offering to do so, but alas often it gets ignored. So on GTA04-goldelico
2012-01-11 09:49 <wolfspraul> well here I hope you recognize we appreciate your input a lot. worst case it's being recorded for the moment, and picked up later.
2012-01-11 09:49 <wolfspraul> wiki, irc logs, etc.
2012-01-11 09:49 <wolfspraul> gta04, don't know. I don't understand the project.
2012-01-11 09:50 <DocScrutinizer51> don't worry, me neither :-D
2012-01-11 09:51 <DocScrutinizer51> the 'funny' detail: again audio section is in top 3 of messed up circuits
2012-01-11 09:53 <blogic> DocScrutinizer51: is audio out hard to layout ?
2012-01-11 09:53 <blogic> i have a board here with i2c/pcm bus and wanted to make a small breakout with a wolfson codec on it
2012-01-11 09:54 <blogic> i got the impression it would be trivial
2012-01-11 09:54 <blogic> but reading your comments i might be mistaken
2012-01-11 10:01 <DocScrutinizer51> nah, audio isn't particularly hard
2012-01-11 10:02 <DocScrutinizer51> wolfspraul: (messed up) in GTA04
2012-01-11 10:02 <DocScrutinizer51> wpwrak: I thought about the CD in a bit more
2012-01-11 10:03 <DocScrutinizer51> the purpose of 'pulldowns' is obvious. But when you wnt that, you need pulldowns to virtual GND, not to real GND
2012-01-11 10:05 <DocScrutinizer51> you may or may not want to tie virtGND to real gnd with a 100kR//1nF then
2012-01-11 10:05 <DocScrutinizer51> bbl, work
2012-01-11 10:24 <qi-bot> [commit] Wolfgang Spraul: Werner: we can drop the ERC pin exceptions patches. (master) http://qi-hw.com/p/eda-tools/78b197d
2012-01-11 10:25 <qi-bot> [commit] Wolfgang Spraul: merged with cmdline patches (master) http://qi-hw.com/p/eda-tools/771599b
2012-01-11 10:51 <qi-bot> [commit] Wolfgang Spraul: patch cleanup (master) http://qi-hw.com/p/eda-tools/724ca1e
2012-01-11 10:56 antoniodariush [antoniodariush!~antonioda@nat-sta-smtc2.tvu.ac.uk] has joined #qi-hardware
2012-01-11 11:21 <qi-bot> [commit] Wolfgang Spraul: updated patchset to kicad rev 3351 (current head) (master) http://qi-hw.com/p/eda-tools/0bdf904
2012-01-11 11:22 <wolfspraul> wpwrak: you can try, I upticked it to 3351 (current latest)
2012-01-11 11:22 <wolfspraul> actually there are so many renames going on they managed to break a few things in the last few days alone
2012-01-11 11:22 <wolfspraul> active project, cannot complain. all the more reason to upstream asap.
2012-01-11 11:23 <wolfspraul> I left out the pin collision patch for now because it's just a few lines, and of course that area changed as well. it's now called 'SynchronizePins()'
2012-01-11 11:23 <wolfspraul> I could uplevel the patch, but that might do more harm than good because I would basically guess the meaning of those variables. better you look at it.
2012-01-11 11:45 <roh> morning
2012-01-11 11:47 rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware
2012-01-11 11:47 skynet-2000 [skynet-2000!~skynet-20@unaffiliated/skynet2000] has joined #qi-hardware
2012-01-11 11:47 mirko [mirko!~mirko@simulachron-81.in-berlin.de] has joined #qi-hardware
2012-01-11 11:47 viric [viric!~viric@unaffiliated/viric] has joined #qi-hardware
2012-01-11 11:47 losinggeneration [losinggeneration!~quassel@71-34-161-176.desm.qwest.net] has joined #qi-hardware
2012-01-11 11:56 cladamw [cladamw!~adamwang@host-222.80-43-115.dynamic.totalbb.net.tw] has joined #qi-hardware
2012-01-11 11:57 <wolfspraul> morning
2012-01-11 12:00 cladamw [cladamw!~Adam@host-222.80-43-115.dynamic.totalbb.net.tw] has joined #qi-hardware
2012-01-11 12:38 <wolfspraul> wpwrak: looking at the m1 board a bit more thinking about the 'expansion system'
2012-01-11 12:38 <wolfspraul> I think the corner around the audio and infrared makes a lot of sense, basically the entire 'upper floor' of that corner can be where the expansion boards can set
2012-01-11 12:39 <wolfspraul> sit
2012-01-11 12:39 <wolfspraul> the other side is crowded with large DMX connectors, video-in, jtag-serial, etc.
2012-01-11 12:50 wolfspra1l [wolfspra1l!~wolfsprau@p5B0ADC9C.dip.t-dialin.net] has joined #qi-hardware
2012-01-11 12:52 AwAyla [AwAyla!~paul@11.241.112.78.rev.sfr.net] has joined #qi-hardware
2012-01-11 13:08 tonghuix [tonghuix!~tonghuix@123.115.192.73] has joined #qi-hardware
2012-01-11 13:11 mstevens [mstevens!~mstevens@fsf/member/pdpc.active.mstevens] has joined #qi-hardware
2012-01-11 13:13 <wpwrak> wolfspra1l: (corner) yes. there's room there. no tall components, plus nothing on the case wall, so one can install a customized wall with openings, if needed
2012-01-11 13:14 tonghuix [tonghuix!~tonghuix@123.115.192.73] has joined #qi-hardware
2012-01-11 13:20 blogic [blogic!~blogic@nbd.name] has joined #qi-hardware
2012-01-11 13:22 <cladamw> wpwrak, one quick question: we short L3 for fixing audio problem in rc3. When routing in rc4, just to use 0 ohm or directly short GND and AUDIO_AGND?
2012-01-11 13:22 <cladamw> wpwrak, this question will be the same as L19 for video.
2012-01-11 13:24 <cladamw> since there's different copper gnd(digital and analog) area splitted.
2012-01-11 13:25 <cladamw> i think that I can just use copper wire to connect/wire two existed ground systems. (i.e. to be the same as rc3 patches now)
2012-01-11 13:27 <cladamw> wpwrak, and keep the existing copper plates not to fill them up. or you have another different thinking?
2012-01-11 13:28 <wpwrak> cladamw: (l3, l19) i'd short directly. l3 and l19 are clearly wrong and keeping them a "0 R" just adds confusion
2012-01-11 13:28 <cladamw> oah~i typed in wrong channel 
2012-01-11 13:28 <cladamw> should go #milkymist
2012-01-11 13:30 blogic [blogic!~blogic@openwrt/developer/blogic] has joined #qi-hardware
2012-01-11 13:50 <wpwrak> wolfspra1l: (pin collision patch) okay, that one can wait a few days. we only need it when editing symbols.
2012-01-11 13:51 <wpwrak> wolfspra1l: (things broken in the last few days) that sounds scary. what sort of breakage ?
2012-01-11 13:55 <wolfspra1l> just renaming again
2012-01-11 13:55 <wolfspra1l> they seem to love renaming
2012-01-11 13:55 <wolfspra1l> I already mentioned it here, case up and down, underscore in and out
2012-01-11 13:55 <wolfspra1l> no consistency either, seems several authors editing each others codes back and forth
2012-01-11 13:55 <wolfspra1l> well then
2012-01-11 13:56 <wolfspra1l> renaming all dialog classes from DIALOG_SOMETHING_BASE to DIALOG_SOMETHING_base begs for another rename :-)
2012-01-11 13:56 <wolfspra1l> mixed-case - bah
2012-01-11 13:58 <wpwrak> at least they're keeping the indentation/whitespace style, aren't they ? it's one of the ugliest i've ever seen, so it's hard to progress from the status quo
2012-01-11 14:00 urandom__ [urandom__!~user@ip-88-152-208-231.unitymediagroup.de] has joined #qi-hardware
2012-01-11 14:00 <wolfspra1l> wpwrak: yes I mostly see battles around underscores and case
2012-01-11 14:01 <wolfspra1l> I replied to my 1-yr old thread on the mailing list :-)
2012-01-11 14:01 <wolfspra1l> not very nice, but what's a good mail client for...
2012-01-11 14:01 <wolfspra1l> at least it wasn't a 10-yr old thread
2012-01-11 14:02 <wpwrak> let's hope people see it. if using a threading MUA, they may not notice
2012-01-11 14:24 wolfspraul [wolfspraul!~wolfsprau@p5B0ADC9C.dip.t-dialin.net] has joined #qi-hardware
2012-01-11 14:32 jow_laptop [jow_laptop!~jow@ffx.subsignal.org] has joined #qi-hardware
2012-01-11 14:49 Textmode [Textmode!~boneidle@adsl-syd-2-209.ozonline.com.au] has joined #qi-hardware
2012-01-11 15:26 paroneayea [paroneayea!~user@fsf/member/paroneayea] has joined #qi-hardware
2012-01-11 15:50 emeb [emeb!~ericb@ip72-223-81-94.ph.ph.cox.net] has joined #qi-hardware
2012-01-11 16:20 rzk [rzk!~rzk@95-25-162-206.broadband.corbina.ru] has joined #qi-hardware
2012-01-11 16:38 stefan_schmidt [stefan_schmidt!~stefan@p4FC77376.dip.t-dialin.net] has joined #qi-hardware
2012-01-11 16:52 rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware
2012-01-11 16:56 kristoffer_ [kristoffer_!~kristoffe@c-e9d8e555.010-30-6c6b7012.cust.bredbandsbolaget.se] has joined #qi-hardware
2012-01-11 18:06 kilae [kilae!~chatzilla@catv-161-018.tbwil.ch] has joined #qi-hardware
2012-01-11 18:23 rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware
2012-01-11 18:46 <viric> I sent the patch
2012-01-11 18:47 <viric> then, why my serial line does not work.grr
2012-01-11 18:47 stefan__ [stefan__!~stefan@p4FC75CC9.dip.t-dialin.net] has joined #qi-hardware
2012-01-11 18:55 <viric> now the serial works. weird.
2012-01-11 18:56 <viric> but it fails sometimes at 57600
2012-01-11 18:58 <viric> how reliable it should be?
2012-01-11 19:04 <larsc> 100%
2012-01-11 19:04 <viric> hm I send 'hello\n' in a loop...
2012-01-11 19:04 <viric> and not all reach fine the other side :)
2012-01-11 19:04 <larsc> hm
2012-01-11 19:05 <viric> maybe it's me with stty, that I don't know how to use it.
2012-01-11 19:05 <larsc> maybe your other side is broken
2012-01-11 19:05 <viric> maybe I have too bad contacts :)
2012-01-11 19:06 <larsc> since there is no flow control the jz4740 will happily send out new bytes whether the other side is ready to receive them or not
2012-01-11 19:07 <viric> hm
2012-01-11 19:07 <viric> not at all?
2012-01-11 19:07 <viric> isn't xon/xoff working? I used "ixon ixoff" in both sides
2012-01-11 19:07 <larsc> hm
2012-01-11 19:07 <larsc> no hardware flow control
2012-01-11 19:07 <viric> I know..
2012-01-11 19:07 <larsc> sw flow control should work
2012-01-11 19:08 <viric> (serial lines, 2012, and still a mistery to get right)
2012-01-11 19:08 FrankBlues [FrankBlues!~alex@c-67-182-230-190.hsd1.ut.comcast.net] has joined #qi-hardware
2012-01-11 19:08 <Ayla> if you have only 3 wires, then there's no hardware flow control
2012-01-11 19:08 <viric> why shouldn't xon/xoff work? it's the OS implementing that, or the uart?
2012-01-11 19:08 <larsc> probably a bit of both
2012-01-11 19:09 <viric> through irqs..
2012-01-11 19:09 <viric> maybe.
2012-01-11 19:09 <larsc> but we use the generic 8250 driver
2012-01-11 19:17 <viric> ok
2012-01-11 19:18 <viric> uhm loading the driver reprograms the line at 57600 I imagine. Because at 9600, I see until the 'serial8250.0' loading :)
2012-01-11 19:27 <viric> [    0.800000] jz4740-nand jz4740-nand.0: No NAND chips found
2012-01-11 19:28 <viric> I have MTD_NAND_JZ4740 enabled...
2012-01-11 19:29 * larsc blames mth
2012-01-11 19:30 <mth> NAND still works fine on the A320 though, I tested that
2012-01-11 19:30 <viric> ehem. this kernel is not in its best moment ;)
2012-01-11 19:30 <viric> Time for kgdb then! :)
2012-01-11 19:32 <viric> what makes the nanonote sometimes turn on at connecting power, sometimes not?
2012-01-11 19:32 <viric> btw, why can't I enable CONFIG_FRAME_POINTER?
2012-01-11 19:33 <viric> maybe they are not required.
2012-01-11 19:33 Ayla [Ayla!~paul@11.241.112.78.rev.sfr.net] has joined #qi-hardware
2012-01-11 19:50 <larsc> viric: thanks for sending the patch
2012-01-11 19:51 <viric> I was only the typing hand
2012-01-11 19:51 <viric> I'm going to play with the uart...
2012-01-11 19:51 <viric> I want the kernel to disable the gpio function of the pin, and use rx...
2012-01-11 19:52 <DocScrutinizer> (xon/xoff) might work suboptimal when TX FIFO isn't handled in a way to place XOFF on top of FIFO, so another 16 or even 64 chars get sent until XOFF gets sent
2012-01-11 19:52 <DocScrutinizer> larsc should know how that's inplemented
2012-01-11 19:53 <viric> DocScrutinizer: so the uart has to help in that
2012-01-11 19:53 <DocScrutinizer> I do't think UART knows XON/XOFF flow control
2012-01-11 19:53 <viric> ah. then? 
2012-01-11 19:53 <DocScrutinizer> driver side implementation
2012-01-11 19:53 <DocScrutinizer> I guess
2012-01-11 19:54 <viric> maybe the driver can be set some chars to bypass the bufefr
2012-01-11 19:54 <DocScrutinizer> the buffer is HW though
2012-01-11 19:54 <DocScrutinizer> FIFO
2012-01-11 19:54 <viric> I know
2012-01-11 19:54 <DocScrutinizer> in UART
2012-01-11 19:54 <viric> but maybe the uart can trigger an irq, if some special char 'enters' the fifo
2012-01-11 19:55 <DocScrutinizer> that had to be checked
2012-01-11 19:55 <viric> or maybe xon/xoff can't replace properly hw flow control
2012-01-11 19:55 <DocScrutinizer> theoretically it's possible
2012-01-11 19:55 <viric> but I think that proper UARTs should be able to use it
2012-01-11 19:55 <viric> (with proper drivers)
2012-01-11 19:56 <viric> http://vicerveza.homeunix.net/~viric/cgi-bin/nanonixos/artifact/3b11d7bf1ea31a579211febf61977d46a8af97e4 my poor start
2012-01-11 19:57 <DocScrutinizer> proper driver: RX congestion -> flush TX FIFO, send XOFF, resend flushed bytes
2012-01-11 19:57 <viric> you should handle the possible deadlock :)
2012-01-11 19:58 <DocScrutinizer> even ignore TX-XOFF state, as XOFF may be sent even when TX is itself blocked by a XOFF
2012-01-11 19:58 <DocScrutinizer> hehe ^^^
2012-01-11 19:58 <viric> I don't find that easy to think about :)
2012-01-11 19:58 <DocScrutinizer> XOFF/XON alway may get sent
2012-01-11 19:59 <DocScrutinizer> always*
2012-01-11 19:59 <DocScrutinizer> IOW, a XOFF may not prevent XOFF/XON to get sent
2012-01-11 19:59 <viric> aha.
2012-01-11 19:59 <viric> I agree
2012-01-11 20:01 <viric> do you have the jz4740pm.pdf somewhere?
2012-01-11 20:01 <DocScrutinizer> me? nope
2012-01-11 20:01 <viric> anyone here
2012-01-11 20:08 <viric> is it secret? :)
2012-01-11 20:22 Ayla [Ayla!~paul@11.241.112.78.rev.sfr.net] has joined #qi-hardware
2012-01-11 20:24 <DocScrutinizer> http://read.pudn.com/downloads160/ebook/723804/Jz4740-spec/Jz4740_ds.pdf hmm, not really good but doesn't mention XOFF IRQ
2012-01-11 20:26 <DocScrutinizer> http://en.ingenic.cn/product.aspx?ID=60
2012-01-11 20:30 <viric> ok ok
2012-01-11 20:32 * DocScrutinizer is feeling nostalgic about times when Zilog shipped their Z80 CPU with a proper paperback 150p manual
2012-01-11 20:32 jekhor [jekhor!~jek@vulture2-nat-41.telecom.by] has joined #qi-hardware
2012-01-11 20:34 <kristianpaul> paperback manual, nice ! i remenber when i used to print datasheets for PICs ;)
2012-01-11 20:38 <larsc> never ever used printed datasheets
2012-01-11 20:40 <kristianpaul> pic18f havent chnaged too much since 3 years i remenber.. i hope ;)
2012-01-11 20:41 <kristianpaul> larsc: yes sure, for that time i dint have laptop and read on CRT display wasnt very nice..
2012-01-11 20:41 <larsc> ah, ok
2012-01-11 20:42 <larsc> as DocScrutinizer said, back in the good old days hardware come with printed manuals
2012-01-11 20:42 <kristianpaul> i always wanted to have a z80... sigh 
2012-01-11 20:44 <larsc> kristianpaul: implement a z80 on the milkymist ;)
2012-01-11 20:44 <kristianpaul> hahah
2012-01-11 20:44 <kristianpaul> you serious?
2012-01-11 20:45 <larsc> sure, why not
2012-01-11 20:45 <larsc> the z80 is rather simple
2012-01-11 20:45 <larsc> iirc
2012-01-11 20:45 <kristianpaul> i agree with lekernel on this :) waste of time (:
2012-01-11 20:46 <kristianpaul> hmm indeed
2012-01-11 20:46 <kristianpaul> where are the multiplers ! :)
2012-01-11 20:53 <DocScrutinizer> http://www.farnell.com/datasheets/50154.pdf
2012-01-11 20:55 <DocScrutinizer> or this one: http://www.ebay.de/itm/IC-Z80B-CPU-Zilog-Z8400BPS-/380137224284?pt=Bauteile&hash=item5881f1b85c
2012-01-11 20:56 <DocScrutinizer> or this  XP : http://www.ebay.de/itm/Zilog-Z80-CPU-Z0840006PSC-9904-2Q-11070-/190616518598?pt=DE_Elektronik_Computer_CPUs&hash=item2c61a13fc6
2012-01-11 21:02 <DocScrutinizer> \o/ ASIO: http://www.ebay.de/itm/IC-BAUSTEIN-Z80ASIO-CPU-17488-129-/170714918488?pt=Bauteile&hash=item27bf66ee58 ; CTC: http://www.ebay.de/itm/IC-BAUSTEIN-Z80CTC-CPU-17493-129-/130590019482?pt=Bauteile&hash=item1e67c58f9a ; PIO: http://www.ebay.de/itm/IC-BAUSTEIN-Z80BPIO-CPU-17492-129-/170714918565?pt=Bauteile&hash=item27bf66eea5
2012-01-11 21:05 <DocScrutinizer> I'd actually consider to buy that one - just because it looks so nice: http://www.ebay.de:80/itm/ws/eBayISAPI.dll?ViewItem&item=250966296618&clk_rvr_id=306143752208&item=250966296618&lgeo=1&vectorid=229487
2012-01-11 21:09 <mth> larsc: there is an open Z80 core for FPGA already
2012-01-11 21:11 <larsc> mth: yea, though so
2012-01-11 21:11 <DocScrutinizer> http://www.reichelt.com/ZILOG-Controller/0/16/index.html?;ACTION=2;LA=2;GROUPID=2951;SID=10Tw36gn8AAAIAAETVBwoa45e26b9203ecd307b36f5b52931f637
2012-01-11 21:11 <mth> it's used in this system: http://www.hat.hi-ho.ne.jp/tujikawa/esepld/
2012-01-11 21:17 <viric> mth: you introduced lots of changes in the nand driver :)
2012-01-11 21:18 <mth> yes, but most of them only affect the behavior after the chips have been detected
2012-01-11 21:19 <viric> hm ah
2012-01-11 21:19 <DocScrutinizer> a last goldie oldie one: http://zilog.com/index.php?option=com_product&task=product&businessLine=1&id=139&parent_id=139&Itemid=59
2012-01-11 21:19 <mth> you can ignore the cc_ftl and A320 patches, they don't apply to NanoNote at all
2012-01-11 21:20 <mth> e7ca5a665877a030c461959c0853e65a346de2de (multi-bank) does change the detection
2012-01-11 21:21 <mth> hmm, "banks = " is missing from board-qi_lb60.c
2012-01-11 21:22 <mth> can you try adding ".banks                  = { 1, 2, 3, 4 }," to qi_lb60_nand_pdata?
2012-01-11 21:23 <mth> is there any variation in the NAND banks of different NanoNotes or is it always the same bank?
2012-01-11 21:23 <viric> ok
2012-01-11 21:25 <viric> I'll try
2012-01-11 21:26 <viric> mth: worked
2012-01-11 21:26 <mth> ok, then larsc was right to blame me ;)
2012-01-11 21:27 <mth> larsc: should I make it search all 4 banks or should I hardcode the actual bank for the NanoNote?
2012-01-11 21:27 <larsc> hm, i think hardcoding ist ok
2012-01-11 21:28 <larsc> is
2012-01-11 21:28 <mth> viric: in which bank was the NAND found? (see dmesg)
2012-01-11 21:29 <viric> [    0.830000] jz4740-nand jz4740-nand.0: Found chip 0 on bank 1
2012-01-11 21:30 <viric> nothing on 2,3,4
2012-01-11 21:30 <mth> ok, thanks
2012-01-11 21:30 <viric> there was in the code: ret = nand_scan_ident(mtd, 1, NULL);
2012-01-11 21:30 <viric> '1' is the bank, maybe.
2012-01-11 21:31 <viric> no idea.
2012-01-11 21:31 <viric> ah, 1 is 'maxchips'.
2012-01-11 21:31 <DocScrutinizer> A nice reading matter: http://www.zilog.com/docs/z80/um0080.pdf p.42ff >>... When an EI instruction is executed, any pending interrupt request is not accepted until after the instruction following EI is executed. This single instruction delay is necessary when the next instruction is a return instruction. Interrupts are not allowed until a return is completed. The... << - I think I learnt all I know about IRQ from Zilog Z80 UM :-D
2012-01-11 21:39 <viric> mth: should I wait for a commit?
2012-01-11 21:43 <qi-bot> [commit] Maarten ter Huurne: MIPS: JZ4740: qi_lb60: Look for NAND chip in bank 1. (jz-3.2) http://qi-hw.com/p/qi-kernel/450999b
2012-01-11 21:43 <viric> oh ok nice
2012-01-11 21:44 <mth> that's a yes :)
2012-01-11 21:53 * wpwrak remembers going to the intel office in zuerich at the age of twelve or so, trying to buy 8080 documentation. they were a bit puzzled but kind enough let me have the manual for free. i still have it. one fun fact is that it mention even the 8088. remarkable long-term planning. needless to say, that was a few years before downloadable pdfs :)
2012-01-11 22:01 <DocScrutinizer> :-D http://www.zilog.com/docs/z80/ps0178.pdf  <- scanned from my original ;-)
2012-01-11 22:03 <DocScrutinizer> wpwrak: I conclude you are some ~7 years younger than me
2012-01-11 22:03 <DocScrutinizer> maybe 5
2012-01-11 22:04 <kristianpaul> lol
2012-01-11 22:07 <wpwrak> ;-)
2012-01-11 22:07 <viric> larsc: I could attach a gdb at boot :) but I forgot the debug symbols
2012-01-11 22:08 <wpwrak> 1967 here
2012-01-11 22:08 <viric> but 'cont' made the kernel boot :)
2012-01-11 22:08 <viric> larsc: I wrote jz_gpio_set_function(JZ_GPIO_UART0_RXD, JZ_GPIO_FUNC_UART0_RXD);   in the 'board_gpio_setup' as a trick to have rx working on ttyS0
2012-01-11 22:09 <larsc> :)
2012-01-11 22:11 <viric> fair? I had no idea what todo
2012-01-11 22:11 <viric> nicer would be a kernel cmdline parameter for that
2012-01-11 22:11 <larsc> looks good
2012-01-11 22:11 <viric> but who knows how to write that
2012-01-11 22:11 <larsc> pretty easy
2012-01-11 22:12 <larsc> there is one for the avt2
2012-01-11 22:12 <larsc> you could use that as a skeleton
2012-01-11 22:12 <viric> what is an avt2?
2012-01-11 22:12 <larsc> it was a experimental nanonote board with usbhost and 64MB ram
2012-01-11 22:13 <viric> not jz4740?
2012-01-11 22:13 <larsc> jz4740
2012-01-11 22:13 <larsc> instead of the jz4725
2012-01-11 22:13 <viric> there is only jz4740 and a320, not?
2012-01-11 22:13 <larsc> hm?
2012-01-11 22:14 <viric> I'll recheck
2012-01-11 22:14 <larsc> in the nanonote board file there is a callback which registers the usb host device
2012-01-11 22:14 <larsc> called avt2_something
2012-01-11 22:14 <larsc> or something_avt2
2012-01-11 22:14 <viric> ah yes
2012-01-11 22:16 <viric> jz4740-ohci?
2012-01-11 22:16 <viric> there are cmdline checks in that driver?
2012-01-11 22:16 <larsc> no in the nanonote board file
2012-01-11 22:16 <viric> hm
2012-01-11 22:17 <larsc> just search for the function name
2012-01-11 22:17 <viric> I couldn't see them then
2012-01-11 22:17 <viric> I think I did
2012-01-11 22:17 <larsc> let me check
2012-01-11 22:17 <larsc> board_avt2 is the function
2012-01-11 22:18 <larsc> and it is hooked up to the avt2 keyword on the commandline via __setup("avt2", board_avt2);
2012-01-11 22:18 <viric> ahh
2012-01-11 22:18 <viric> I had no idea that was a hook
2012-01-11 22:23 <DocScrutinizer51> wpwrak: so my initial guess was absolutely correct :-) tell me which CPU you used and I tell you how old you are
2012-01-11 22:25 <wpwrak> ;-)
2012-01-11 22:26 <Ayla> DocScrutinizer51: Pentium 3
2012-01-11 22:26 <Ayla> ?
2012-01-11 22:26 <larsc> DocScrutinizer51: my first cpu was a pentium I 90 Mhz
2012-01-11 22:26 <Ayla> how old am I? :D
2012-01-11 22:27 <Ayla> logically, I'm a lot younger than larsc 
2012-01-11 22:27 <DocScrutinizer51> too young :-D
2012-01-11 22:28 <larsc> and my first "compiler" visual studio c++ 6.0
2012-01-11 22:28 <wpwrak> eek
2012-01-11 22:29 <larsc> hehe :)
2012-01-11 22:29 <wpwrak> glad you managed to become a decent person despite the abuse you suffered in your youth :)
2012-01-11 22:30 <wpwrak> or maybe it was that what instilled a strong willingness to escape the misery
2012-01-11 22:30 <viric> hm I don't manage to debug with kgdb.
2012-01-11 22:30 * nbd started with a cyrix 486 DX and turbo pascal ;)
2012-01-11 22:31 <Jay7> turbo pascal is the best!
2012-01-11 22:31 * Jay7 started from P1 100Mhz w/o MMX
2012-01-11 22:31 <Jay7> 16Mb RAM btw..
2012-01-11 22:31 * wpwrak wonders if psychoanalysts ask hackers about their first cpu and compiler. these two are probably a lot more influential on the shape of the blossoming mind than, say, parents
2012-01-11 22:31 <Jay7> but before was ZX Spectrum :)
2012-01-11 22:33 <Ayla> actually I started with a 6MHz Z80 CPU
2012-01-11 22:33 <Ayla> and 32kB of RAM
2012-01-11 22:35 <wpwrak> Ti 57, 50 program steps, 8 data registers
2012-01-11 22:36 <viric> it looks like the vmlinux addresses don't match those of runtime at the nanoonte
2012-01-11 22:38 <larsc> wpwrak: and my first book on programming book 'c++ in 30 days'
2012-01-11 22:40 <Jay7> larsc: I have that book :)
2012-01-11 22:40 <viric> hm
2012-01-11 22:40 <Jay7> or may be similar at least
2012-01-11 22:40 <viric> larsc: the kernel is not loaded at the addresses the vmlinux elf says
2012-01-11 22:42 <larsc> by whom?
2012-01-11 22:42 <viric> by my xbboot command
2012-01-11 22:44 <larsc> viric: the load address or the entry point address is wrong?
2012-01-11 22:44 <viric> hm I don't know
2012-01-11 22:44 <viric> when I attach gdb, it sayas:
2012-01-11 22:44 <viric> syas
2012-01-11 22:44 <viric> says
2012-01-11 22:44 <viric> #0  0x81c5274f in ?? ()
2012-01-11 22:44 <viric> while 'info file', says:
2012-01-11 22:44 <viric>         0x80010000 - 0x803210c8 is .text
2012-01-11 22:46 <larsc> is the kernel halted when you attach gdb?
2012-01-11 22:46 <viric> I used the vmlinuz load address calculation, and uploading to  that... it boots fine too, but gives the same gdb symbol strouble
2012-01-11 22:46 <viric> larsc: yes yes. if I write 'cont', it continues
2012-01-11 22:46 <viric> But why is it at 0x81c5274f, I don't know
2012-01-11 22:47 <larsc> viric: have you tried break some_kernel_symbol? The address you see above is probably just some userspace process
2012-01-11 22:47 <viric> I tried
2012-01-11 22:47 <viric> larsc: I use 'kgdbwait'. it's halted just after the serial driver got loaded.
2012-01-11 22:47 <viric> (no user space)
2012-01-11 22:47 <larsc> ah, ok
2012-01-11 22:48 <viric> 'disasm' fails
2012-01-11 22:48 <viric> I mean, that 'disasm symbol' does not disassemble the symbol
2012-01-11 22:48 <viric> :)
2012-01-11 22:48 <larsc> hm
2012-01-11 22:50 <viric> I think the bad boot messages mean: uncompressing kernel at address 80010000
2012-01-11 22:50 <viric> (there are some characters 'eaten' there... the early console may be working bad)
2012-01-11 22:50 <viric> 80010000 is the vmlinux load address.
2012-01-11 22:53 <viric> hm I see the vmlinuz address is not very important.
2012-01-11 22:53 <viric> it has to be valid, and it shouldn't be overwritten by decompression :)
2012-01-11 23:12 <viric> larsc: using kdb, it looks fine.
2012-01-11 23:12 <viric> with gdb, bad.
2012-01-11 23:12 <viric> oh
2012-01-11 23:12 <viric> I forgot to start the *mipsel* gdb.
2012-01-11 23:14 <DocScrutinizer> wpwrak: EEEEK TI
2012-01-11 23:14 <viric> stupid me
2012-01-11 23:14 <viric> it works perfect
2012-01-11 23:14 <DocScrutinizer> HP-25 here
2012-01-11 23:14 <viric> kgdb working!
2012-01-11 23:19 <DocScrutinizer> wpwrak: and we coded everything from "shortest fastest prime factoring" over "mastermind" and "guess the atom"(send ray in a grid, see where it exits), to auto-adjusting converters for Philips cassette tape counter to real playtime (sub minute accuracy) and even stopwatches (a pity on that "platform", we learnt a lot though about how the CPU works :-D)
2012-01-11 23:20 <DocScrutinizer> e.g. execution speed for a particular instruction was a sawtooth function vs the location in "RAM" of that instruction
2012-01-11 23:20 <DocScrutinizer> and of course the whole thing was highly ambient temperature susceptible
2012-01-11 23:22 <DocScrutinizer> and the best time to compete on all those nice efforts was during english and physics lessons ;-D
2012-01-11 23:22 <wpwrak> i mainly wrote games in my early years :)
2012-01-11 23:23 <viric> larsc: so, enough for today. Victory!
2012-01-11 23:27 <viric> mth, Ayla, larsc: http://vicerveza.homeunix.net/~viric/cgi-bin/nanonixos/doc/trunk/doc/kerneldbg/index.wiki
2012-01-11 23:31 <larsc> nice
2012-01-11 23:32 <Ayla> I see that you define the root filesystem as being UBI
2012-01-11 23:32 <Ayla> and I remember the nanonote uses UBI too (IIRC)
2012-01-11 23:32 <viric> Ayla: well, that's what I have in the nand
2012-01-11 23:32 <Ayla> how do you guys boot to UBI? I thought u-boot didn't support it
2012-01-11 23:32 <viric> the kernel is in a nand partition directly
2012-01-11 23:32 <viric> not in a file
2012-01-11 23:33 <Ayla> ah, ok
2012-01-11 23:33 <viric> there are 4MiB for it.
2012-01-11 23:33 <viric> although uboot loaded only 2MiB (cough)
2012-01-11 23:33 <Ayla> I started a new bootloader for JZ-based devices,
2012-01-11 23:33 <viric> ah
2012-01-11 23:34 <viric> how so?
2012-01-11 23:34 <Ayla> it's called UBIBoot because it boots to UBI
2012-01-11 23:34 <viric> to a file in an ubifs?
2012-01-11 23:35 <Ayla> no, to a kernel flashed on a UBI volume
2012-01-11 23:35 <viric> ah
2012-01-11 23:35 <viric> why not implement that on uboot?
2012-01-11 23:36 <Ayla> well, I wanted to create a bootloader myself :)
2012-01-11 23:36 <viric> ah ok
2012-01-11 23:37 <Ayla> back on topic - good job with kgbd
2012-01-11 23:37 <viric> I like when people write on the documents what they type and also what they see as result :)
2012-01-11 23:38 <viric> I remembe as if the qihw wiki had too much of 'type that', without result
2012-01-11 23:40 <viric> ok, sleep.
2012-01-11 23:40 <viric> Goedenacht
2012-01-11 23:45 <DocScrutinizer> now uBoot bashing continues *here* ? :-S
2012-01-11 23:59 zrafa [zrafa!~rafa@186.137.0.13] has joined #qi-hardware