Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
urandom__ [urandom__!~user@p548A4CA4.dip.t-dialin.net] has joined #qi-hardware
jekhor_ [jekhor_!~jek@vulture2-nat-45.telecom.by] has joined #qi-hardware
paroneay` [paroneay`!~user@c-67-175-218-235.hsd1.il.comcast.net] has joined #qi-hardware
skynet-2000 [skynet-2000!~skynet-20@unaffiliated/skynet2000] has joined #qi-hardware
DocScrutinizer [DocScrutinizer!~halley@openmoko/engineers/joerg] has joined #qi-hardware
pabs3 [pabs3!~pabs@d175-38-164-81.per801.wa.optusnet.com.au] has joined #qi-hardware
kilae [kilae!~chatzilla@catv-161-018.tbwil.ch] has joined #qi-hardware
Ayla [Ayla!~paul@9.95.112.78.rev.sfr.net] has joined #qi-hardware
<viric>
larsc: I'll enjoy putting a breakpoint on fb_notifier_callback :)
qwebirc63466 [qwebirc63466!451ec28b@gateway/web/freenode/ip.69.30.194.139] has joined #qi-hardware
Ayla [Ayla!~paul@9.95.112.78.rev.sfr.net] has joined #qi-hardware
jluis [jluis!~jluis@176.Red-81-38-165.dynamicIP.rima-tde.net] has joined #qi-hardware
tonghuix [tonghuix!~tonghuix@221.219.121.123] has joined #qi-hardware
Ayla [Ayla!~paul@28.95.13.93.rev.sfr.net] has joined #qi-hardware
rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware
antoniodariush [antoniodariush!~antonio@host-92-18-38-70.as13285.net] has joined #qi-hardware
Textmode [Textmode!~boneidle@adsl-syd-2-209.ozonline.com.au] has joined #qi-hardware
xiangfu [xiangfu!~xiangfu@fidelio.qi-hardware.com] has joined #qi-hardware
<viric>
larsc: I just saw that ret = ili8960_write_reg(spi, ILI8960_REG_POWER, enabled ? 0xc7 : 0xc6); does not power out the lcd
<viric>
ah, enabled equals true.
<DocScrutinizer>
moo
kristoffer [kristoffer!~kristoffe@host-95-206-8-253.mobileonline.telia.com] has joined #qi-hardware
wolfspra1l [wolfspra1l!~wolfsprau@p5B0AC7A7.dip.t-dialin.net] has joined #qi-hardware
rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware
<viric>
enabled means "blank enabled"
<viric>
and it ends up being as 'power enabled'...
<Ayla>
the LCD may be powered on low state
<Ayla>
that is, when the GPIO is zero, the LCD is off
<viric>
Ayla: you think that a call named ili8960_programm_power, would have a parameter 'enabled' that means poweroff if true?
<viric>
on purpose, I mean ;)
<Ayla>
that's probably a mistake then
<viric>
I can't find docs about the 'ILI8960'
<viric>
Ayla: this gdb thing is very nice :)
<Ayla>
I actually never used it
<viric>
(ah, found the ds)
<viric>
aha, looks lke a mistake.
<viric>
if enabled, sets 'normal operation'. If !enabled, sets standby mode.
<viric>
ah maybe I'm wrong. I missed some cod.e
<viric>
hm the code looks fine, until the spi_write
<viric>
the FB_BLANK looks like simply setting the 'standby' mode in the lcd...
<viric>
well, larsc looked like knowing what t odo
<viric>
larsc: to me, jz-3.2 looked like having those patches, and even the lcd answering those events.
<viric>
ah no
<viric>
bad reading
<mth>
jz-3.2 should be getting those patches, but the patches alone without any new callbacks being registered were useless, so I didn't import them yet
<viric>
mth: aren't those callbacks trivial?
<mth>
I don't know, I didn't look into it yet
<viric>
hm it would help if I understood what are those patches for. what problem they try to solve
<viric>
mth: aren't those patches already in mainline 3.2?
<larsc>
viric: the lcd needs to be put into standby before the pixel clock is turned off
<viric>
ahhh
<larsc>
and only brought out of standby after the pixel clock has been re-enabled
<viric>
larsc: and the "fb_notifier_call_chain(FB_EARLY_EVENT_BLANK, &event);" turns the clock off?
<viric>
*sorry*
<viric>
FB_EVENT_BLANK
<larsc>
yes
<viric>
what sets the order of whats get called first, clock off or lcd off?
<viric>
both are in the call chain, iiuc
<larsc>
with the code as it is right now the clock will be turned off first
<viric>
I think the patches are for "cancelling" an event_blank
<viric>
not for changing any order
<larsc>
as the notifier will be called after the framebuffer has been disabled
<larsc>
the patches introduce a new notifier which is called before the framebuffer gets disabled
<viric>
but the purpose of the patches is to be able to cancel the blank
<larsc>
and we want to hook the lcd disable to the new notifier
<larsc>
no it is not
<viric>
ah
<viric>
so, for your purpose, FB_EARLY_EVENT_BLANK would be enough
<viric>
but the patches introduce EARLY and R_EARLY
<larsc>
that's because we need a mechanism to tell a device which listens to a EARLY event that the actuall blanking has failed
<viric>
what determines the order in the fb_notifier_call_chain? the order of calls to fb_register_client() I imagine...
<viric>
Isn't there any system, before the EARLY patches, to determine the order of 'clock shutdown' and 'lcd standby'
<viric>
?
<viric>
(I'm reading do_blank_screen())
xiangfu [xiangfu!~xiangfu@fidelio.qi-hardware.com] has joined #qi-hardware
<viric>
larsc: sorry if I ask too much. :) I'm zero experienced in all this
<larsc>
the clock is disabled in the framebuffer blank callback, which is called before the notifier chain
<viric>
so we are single in the world of devices that have the trouble about clock/lcd-standby?
<larsc>
viric: fetching the tags should be enough
<viric>
ah kernel.org is up again?
<larsc>
viric: no. samsungs seems to have the same issue. the patch which adds the early callback was from an samsung employee
<viric>
'git fetch -t URL' ?
<viric>
I'm trying that
<viric>
hm it's getting lots of objects.
<viric>
larsc: ah ok perfect.
<viric>
larsc: you knew more than what I read in those commit logs!
<viric>
people should write in the commit logs what problem they try to fix...
<mth>
I used "git remote add"
<viric>
that has always been for me a big problem reading most public commits... people forgetting to write what problem they had before the patch.
<larsc>
hehe
<viric>
The solution is in the code. But the problem... it's either in the commit log or nowhere
<mth>
kernel.org was reopened around the same time that 3.2 was released
<mth>
for 3.1 I had git://github.com/torvalds/linux.git as upstream
<viric>
aha ok
<viric>
mth: adding that remote... also fetches a lot, no?
<mth>
it fetches the full history of the kernel
<viric>
can I pick less than that?
<mth>
but probably most of it overlaps with what is already downloaded as part of the qi history
<larsc>
you should already have most of the history if you have jz-3.2
<viric>
hm it picks up a lot.
<mth>
I don't know, I just downloaded everything
<viric>
it'll take 2 or 3 minutes...
<viric>
fine.
<viric>
ok, then, thank you all. I'm up to date with the lcd problem
<viric>
don't you commit things in the kernel like: "/* JZ-TODO: port that patch */" ?
<viric>
(at the moment you did not pick that thing from 3.1)
<viric>
I mean... where is the list of "This needs to be done for jz-3.2"?
<mth>
I gave a short overview on this channel
<mth>
should be in the IRC logs
<viric>
hehe
<viric>
mth: why not have that in the kernel vcs, in the jz-3.2 branch? either in a file, or comments anywhere
<mth>
in the night from 5 to 6 January
<viric>
(searching the log...)
<viric>
found
<viric>
ok
<viric>
nice notes.
<viric>
whitequark: did you say (that day) that the xilinx webpack sends your netlists to xilinx?
<viric>
whitequark: I recall it asking questions about accepting that or not, and they let you answer 'dont send'.
<wolfspra1l>
viric: are you aware of llhdl ?
<viric>
from lekernel?
<wolfspra1l>
it's a long-term project to try to open up some of the synthesis toolchain, Sebastien took a good real first step coding at it, but right now it's dormant until ... don't know. but it's so fundamental it will surely continue.
<wolfspra1l>
yes
<wolfspra1l>
just because we chat about synthesis tools, so I thought I mention it in case it's not known
<viric>
I remember when he was starting...
<viric>
but I did not hear beyond that
<wolfspra1l>
I think it progressed a decent bit, but right now it's dormant.
<viric>
last commit on march 2011?
<wolfspra1l>
to be continued :-)
<wolfspra1l>
sure, could be
<viric>
ok
<viric>
did lekernel get an employer? :)
<wolfspra1l>
we try to build Milkymist One into a business, or other Milkymist derived products
<viric>
ok
<viric>
nice
<wolfspra1l>
but no employer
<wolfspra1l>
yeah it's great
<viric>
you're brave people :)
<wolfspra1l>
nah, it's easy. only do what you really believe in.
<viric>
but then you get in love with a woman that has some incompatible beliefs and...
<viric>
if all were so easy... ;)
<whitequark>
viric: I think if you answer "don't send", they do not compile it
<mth>
if you want to look at the nand contents, it might be simpler to see if you can find a firmware restore ("unbrick") image
<mth>
you could try to open the device and read the NAND chip model from the chip itself
<mth>
that should tell you things like bus width and page size
<mth>
(by data sheet from the manufacturer site)
<bbbb>
mth: still haven't figured out who produces this thing, ok, I am waiting for a triwing screwdriver
<mth>
ah, nasty screws... the Dingoo A320 just uses philips head (cross) screws
<bbbb>
:) yes, they copied the whole gameboy design even the stupid screws
<viric>
ah the stupid gameboy screws...
<whitequark>
try a kinfe
<whitequark>
*knife
<whitequark>
with a little bit of skill it works surprisingly well
urandom__ [urandom__!~user@p548A270F.dip.t-dialin.net] has joined #qi-hardware
<Ayla>
does it have a gameboy cartridge port as well?
<bbbb>
Ayla, yes but I havend figured out what it does
<mth>
is there an actual connector in there or just a hole in the casing?
<bbbb>
*haven't
<bbbb>
mth: connector is there, when I have an screwdriver we know if it is connected :D
<larsc>
the coments on the page say it plays gba cartridges
<viric>
bbbb: for usbboot, you simply use their 'data cable'?
<bbbb>
viric: yes
<viric>
perfect
<viric>
how did you get in usbboot mode?
<viric>
is it a peculiarity of all jz47*?
<mth>
on the A320 it's done by pressing the B key during power up
<viric>
but it's a hw thing that triggers that mode?
<viric>
I thought it was some software somewhere
<larsc>
it's usually connected to a button
<viric>
ah nice
<mth>
it needs a pin pulled down to go into USB boot mode
<larsc>
you just have to figure out which one
<bbbb>
yes, brutforce, gamebox uses the start butotn
<bbbb>
*button
<viric>
wpwrak: do you know if those 8051-like chips (F321?) have something like that, so I could pick the program inside using the usb?
<whitequark>
viric: f321... sounds familiar. is that Cypress?
<mth>
bbbb: do you know the screen resolution? 320x240 or 240x160 or something else?
<bbbb>
mth: good question
<bbbb>
mth: brb testing
<wpwrak>
viric: err, like what ? i've implemented DFU for the f321. with that, i can read/write the firmware
jluis [jluis!~jluis@2001:5c0:1400:a::e8b] has joined #qi-hardware
<viric>
wpwrak: ah, but on a 3rd-party f321... nothing, I imagine
<viric>
whitequark: I can't recall the manufacturer
<viric>
what was first, the kernel and usbboot for the nanonote, or the nanonote was chosen as there was some part of kernel+tools for jz?
<wpwrak>
viric: unless they found my code and reused it :)
<viric>
aha! ok ;)
jluis [jluis!~jluis@176.Red-81-38-165.dynamicIP.rima-tde.net] has joined #qi-hardware
<whitequark>
hm
<whitequark>
if there's anyone from Moscow here, and you want to buy something from http://iteadstudio.com/, then you have a few hours to say what exactly
<whitequark>
why a few hours? because I'm doing an order today, and after that they stop to receive orders due to some chinese festival
<whitequark>
*after this day.
<wpwrak>
Chinese New Year. that's when all of china shuts down.
<wpwrak>
for one week, plus travel. can be a nasty surprise for westeners who want to produce something just around that time and don't know of that holiday :)
emeb [emeb!~ericb@ip72-223-81-94.ph.ph.cox.net] has joined #qi-hardware
<viric>
anyone good at stepper motors?
<viric>
I'd like substepping without annoying whistle noise)
<whitequark>
interesting
<whitequark>
what exactly causes that noise?
<viric>
I think it's the PWM for substepping
* whitequark
does not know how substepping works
<viric>
instead of switching between direct or reverse full currents per phase...
<viric>
you use PWM to achieve currents between 0 and the maximums
<wpwrak>
viric: there are a lot of people who are profoundly convinced in their creative abilities being limited to the immaterial domain
<wpwrak>
as in "we can hack it open but there's no way we could build anything even remotely similar"
<wpwrak>
early fish may have thought pretty much the same about lots of things :)
<viric>
I'm very impressed, by what people achieve, breaking into closed hw
<viric>
And a lot of that "lives" in quite populated web forums, where people design mini-circuits to make parts work... hack firmwares, deciphers the ciphered, ... finds jtags, ...
<viric>
and all looks like web pages or forums of car painters or so.
<wpwrak>
well yes ... it's kinda like neanderthals successfully smuggling them aboard a space shuttle
<wpwrak>
sure, impressive. but does this make them a space-faring civilization ?
<viric>
I mean
<wpwrak>
no, it's "i'm mean" :)
<viric>
how do they manage to decipher those things, hack the bootloaders, put their own...
<viric>
And that people use interchange *compiled* programs
<viric>
instead of source
<wpwrak>
exercises in futility. on both sides :)
<viric>
"I'm mean"? :)
<viric>
and what are the sides?
<wpwrak>
(closed) makers vs. openers :)
<viric>
ahh
<viric>
well, sometimes those help in finding GPLed parts :)
<viric>
and getting manufacturers to publish
<viric>
But I feel like there are crowds of people in those forums that understand quite well electronics, understand linux, mips, whatever board details and devices there...
<wpwrak>
occasionally perhaps. not very often.
<wpwrak>
"street pressure" doesn't work well with megacorps
<wpwrak>
even pitiful competition. that scares them beyond belief.
<viric>
I understand you
<wpwrak>
because they're well aware of their inability to innovate
<viric>
ah, you think that people can know well hacking all that, and then lack to innovate?
<viric>
I wonder what they work to get money
<viric>
work on.
<whitequark>
most people get money for doing nothing
<larsc>
nah, not most, about half of the i'd say
<wpwrak>
no .. the people from the big corps are the ones who can't innovate
<wpwrak>
the ones reverse engineering are the ones who merely choose not to
<viric>
:)
<wpwrak>
larsc: in which half did they put you ? :)
<larsc>
wpwrak: i'm not quite sure yet
<wpwrak>
;-))
wolfspraul [wolfspraul!~wolfsprau@p5B0AC7A7.dip.t-dialin.net] has joined #qi-hardware
paroneay` [paroneay`!~user@c-67-175-218-235.hsd1.il.comcast.net] has joined #qi-hardware
<viric>
wpwrak: where would be openwrt used by nanonote, if it weren't for reverse engineers? :)
<whitequark>
openwrt isn't related to reverse engineering
<whitequark>
it is a linux distro for routers. nothing more.
<whitequark>
how did you get kernel sources isn't actually related to the nature of openwrt
pabspabspabs [pabspabspabs!~pabs@d175-38-164-81.per801.wa.optusnet.com.au] has joined #qi-hardware
<viric>
for closed-hardware routers
<viric>
mostly, no?
<viric>
even the name comes from those linksys
rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware
<wolfspraul>
without having read up on the whole thread, from my personal experience I can say that if you stay within the realm of reverse engineering, you have no chance to grasp the economics of hardware
<wolfspraul>
whether that's design, testing, manufacturing, repair and recycling, logistics, etc.
<wolfspraul>
I think that's a problem
<wolfspraul>
I did reverse engineering for at least 10 years, in all sorts of areas, yet when I started with hardware around 2007, I was completely clueless. hardware was this big black box out of the magic copy machine that is China.
<wolfspraul>
unfortunately I think we must be allowed to say that a majority of free (and other) software engineers are still at this level
<wolfspraul>
the way to get out of that trap is to get out of the reverse engineering mindset, and instead start to do something by yourself, from scratch. create. reverse engineering is not bad, but if that's all you do I think you will hit a ceiling fast.
<wolfspraul>
that's my 2cents :-)
<larsc>
viric: i just wanted to try xbboot, but i'm always getting -110