| 01:41.50 | *** join/#openezx nooop (n=noop@59.62.6.173) |
| 03:21.49 | *** join/#openezx flyhorse|linux (n=flyhorse@125.93.110.133) |
| 05:40.36 | *** join/#openezx WM (i=wyrm@20158215017.user.veloxzone.com.br) |
| 06:52.49 | *** join/#openezx AndiM (n=andi@p50815AB2.dip.t-dialin.net) |
| 07:02.55 | *** join/#openezx drath_ (i=vmaster@p5B07C32C.dip.t-dialin.net) |
| 07:41.26 | *** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1) |
| 08:15.46 | Hopscotch | good morning |
| 09:13.36 | *** join/#openezx z72ka (n=hermanj@r5af183.net.upc.cz) |
| 09:47.55 | *** join/#openezx LuitvD (n=luitvd@beigetower/luitvd) |
| 10:07.30 | *** join/#openezx ljp (n=lpotter@203.94.178.46) [NETSPLIT VICTIM] |
| 10:07.30 | *** join/#openezx Dominus (i=unices@ip5652ade4.speed.planet.nl) [NETSPLIT VICTIM] |
| 10:07.30 | *** join/#openezx TommyMT (n=tk@touchdown.maintech.de) [NETSPLIT VICTIM] |
| 10:09.43 | *** join/#openezx Hopscotc1 (n=cd@touchdown.maintech.de) |
| 10:18.25 | *** join/#openezx florian (n=fuchs@217.146.132.69) |
| 12:09.46 | *** join/#openezx florian (n=fuchs@217.146.132.69) |
| 13:46.15 | *** join/#openezx LuitvD (n=luitvd@beigetower/luitvd) |
| 14:18.28 | *** join/#openezx flyhorse1 (n=flyhorse@219.132.254.28) |
| 15:07.56 | *** join/#openezx nusk (n=pedro@189.27.11.183.adsl.gvt.net.br) |
| 16:12.00 | *** join/#openezx stefan_schmidt (n=stefan@sirius.lasnet.de) |
| 17:17.12 | *** join/#openezx LuitvD_ (n=luitvd@beigetower/luitvd) |
| 17:27.26 | AndiM | hi |
| 17:28.10 | *** join/#openezx pleemans (n=peter@d51A5E76A.access.telenet.be) |
| 17:45.55 | *** join/#openezx tombhadAC (n=tombhad@pD95DD155.dip.t-dialin.net) |
| 17:47.04 | tombhadAC | hi |
| 17:59.16 | AndiM | hi |
| 18:11.57 | *** join/#openezx BadCluster (n=badclust@200.26.114.37) |
| 18:12.14 | *** part/#openezx BadCluster (n=badclust@200.26.114.37) |
| 18:23.36 | stefan_schmidt | AndiM: Are you working on x86_64, i386 or something else? |
| 18:29.52 | stefan_schmidt | A precompiled toolchain for x86_64 for testing: http://people.openezx.org/stefan/tmp/angstrom-x86-64-armv5te-linux-gnueabi-toolchain.tar.bz2 |
| 18:30.10 | stefan_schmidt | i386 will follow in some hours, notebook is to slow :) |
| 18:30.45 | stefan_schmidt | Would good to get some testing for them later. |
| 18:31.14 | stefan_schmidt | As they are build with OE and can get integrated back into the build I would propose them as the official ones. |
| 18:31.59 | stefan_schmidt | So we have a reference. People using others are fine, but on their own for problems. |
| 18:40.58 | *** join/#openezx jannu (n=jannu@hoas-fe3cdd00-15.dhcp.inet.fi) |
| 18:49.14 | LuitvD | stefan_schmidt: shouldn't you give them a more "permanent" location on the interwebs then? |
| 18:49.29 | stefan_schmidt | LuitvD: sure, sure |
| 18:49.31 | LuitvD | stefan_schmidt: /tmp doesn't really look "official" |
| 18:49.33 | LuitvD | :P |
| 18:49.49 | stefan_schmidt | LuitvD: Once they are tested and we settled to use them |
| 18:50.06 | LuitvD | stefan_schmidt: ah, right (for once I'm ahead of things :P lol) |
| 18:50.09 | stefan_schmidt | they will land on openezx.org/downloads/toolchains or something similar |
| 18:50.21 | LuitvD | great :) |
| 18:50.33 | stefan_schmidt | Was just easier for me having them there now |
| 18:50.48 | LuitvD | I'll definately will use them... |
| 18:50.58 | stefan_schmidt | :) |
| 18:51.07 | LuitvD | even for non-ezx stuff :) |
| 18:51.37 | stefan_schmidt | Well then you of course make sure that all optimazations are right |
| 18:52.06 | stefan_schmidt | Anyway, back to preparing something else now. :) |
| 18:52.16 | *** join/#openezx yansa (n=yans@host-89-167-37-237.pronet.lublin.pl) |
| 18:52.38 | LuitvD | (hm, probably not for non-ezx stuff... my ARM board is armv5te too though :) |
| 18:53.34 | LuitvD | (damn, wrong again, it's ARMv4T |
| 18:53.57 | LuitvD | a.k.a. ARM7TDMI ) |
| 18:54.59 | LuitvD | I'll have to compile my own toolchain for that... :( |
| 18:55.28 | stefan_schmidt | LuitvD: So start learning OE better. :) |
| 18:56.02 | LuitvD | ah well, soon enaugh :P |
| 18:58.53 | AndiM | stefan_schmidt: i386 (K7) |
| 18:59.30 | stefan_schmidt | AndiM: ok, then I hopefully have a toolchain for you in an hours or so |
| 18:59.49 | AndiM | stefan_schmidt: argh, and you're doing this now, just when I realized that I had a non-kernel toolchain and corrected this to be the right one ;) |
| 18:59.56 | stefan_schmidt | AndiM: I know you have one now, but I would prefer if people would use the same. Less error prone |
| 19:00.11 | stefan_schmidt | AndiM: heh, everyday a new one... ;) |
| 19:00.13 | AndiM | stefan_schmidt: I don't mind swapping too much. |
| 19:00.34 | stefan_schmidt | AndiM: Should hopefully be the last swap for the next months |
| 19:00.43 | AndiM | but I'll do this later. I want to submit my stuff first (possibly even in non-working state, but it's a whole new driver) |
| 19:01.14 | stefan_schmidt | AndiM: I understand that some people don't like to build them with OE. So havinf the same prebuild is the best way IMHO |
| 19:01.31 | stefan_schmidt | AndiM: Sure, over the WE would be fine with me |
| 19:02.00 | AndiM | stefan_schmidt: for non-packaging work going full OE doesn't make too much sense when time-strapped. |
| 19:02.02 | stefan_schmidt | AndiM: (patches) Send them to the ml. Hopefully someone will jump on and review |
| 19:02.08 | AndiM | sure. |
| 19:02.28 | stefan_schmidt | AndiM: Jup, using a tree outside for kernel hacking here, too. |
| 19:03.12 | AndiM | I'm currently having lots of fun with trying to get some Camera Interface patchwork up and running, to finally get the i2c bus to work ;) |
| 19:03.53 | stefan_schmidt | heh, sounds indeed like fun |
| 19:04.12 | stefan_schmidt | Using the latest patches LAK and v4l? |
| 19:04.23 | AndiM | "oh, I need this one definition" - "ah, that's in this header" - "oh, now I need those other 15 definitions" ;) |
| 19:05.09 | AndiM | stefan_schmidt: nope, just .24 quilt. I intended to go "power-up-only", not do some full camera interfacing. |
| 19:05.21 | stefan_schmidt | ah |
| 19:06.05 | AndiM | I don't remember whether I asked already whether there are details about camera connections. Camera is connected to i2c (AP) and AP (camera interface) only, right? |
| 19:06.40 | stefan_schmidt | IIRC yes |
| 19:06.55 | AndiM | or does someone actually know what kills my i2c comm? |
| 19:07.09 | stefan_schmidt | There are some patches for the camera interface on v4l and LAK some days ago |
| 19:07.19 | stefan_schmidt | (i2c) nope |
| 19:07.21 | AndiM | do those EZX devices do some abuses of power i2c bus? |
| 19:07.50 | AndiM | In that case the camera might be located there and not be the cause for primary i2c bus malfunction. |
| 19:08.04 | stefan_schmidt | hmm, never played with i2c on them. And honestly the last time I really hacked on the code was on .21 :( |
| 19:08.47 | AndiM | how easy would you think it is to get those camera patches up and running? since that would obviously solve my power-up problem, too... |
| 19:09.59 | stefan_schmidt | AndiM: Well, no idea. They are tested on PXA27x, but with a different sensor... |
| 19:10.25 | AndiM | ok, thanks. too much talk and not enough work here ;) need to actually work on it... |
| 19:11.07 | stefan_schmidt | :) |
| 19:11.12 | AndiM | OTOH it's always important to collect knowledge about what is supposed to be done. otherwise one may waste months trying to do the entirely wrong thing :) |
| 19:11.47 | stefan_schmidt | Sure |
| 19:12.13 | stefan_schmidt | I don't mind questions. It's just that I'm not up-to-date |
| 19:13.07 | AndiM | another random question: what do you think is the environment we should concentrate on since it's most lucrative? openmoko, right? |
| 19:14.39 | stefan_schmidt | AndiM: It's the most suited one for cellphones yet. |
| 19:14.57 | stefan_schmidt | AndiM: Still there is much stuff hardcoded for the Neo :( |
| 19:15.14 | stefan_schmidt | AndiM: Another candidate is GPE Phone edition |
| 19:15.23 | AndiM | I have to admit that Iwasn't too impressed with the unstable branch, though ;) kept bringing up weird empty notification bars every second, probably done by notification-daemon or so. |
| 19:15.51 | AndiM | (notification-daemon was most active in top) |
| 19:15.54 | stefan_schmidt | AndiM: yup, it's notification about connected to a gsm cell |
| 19:16.08 | stefan_schmidt | There was a bug that showing it again and again |
| 19:16.57 | AndiM | "was" or "is"? That's the question I'd like to see answered most ;) |
| 19:17.15 | stefan_schmidt | AndiM: IIRC it'S fixed |
| 19:17.21 | AndiM | phew. |
| 19:17.32 | AndiM | now THAT was annoying as hell. |
| 19:17.44 | stefan_schmidt | But it's always a long way from a fix on the developer machine to the user |
| 19:18.16 | AndiM | that's why I need to submit my patches ASAP ;) |
| 19:18.49 | stefan_schmidt | Indeed |
| 19:20.15 | *** join/#openezx flo_lap (n=fuchs@f048071247.adsl.alicedsl.de) |
| 19:20.59 | AndiM | I'm afraid that Neo should then be adapted to use my amplifier driver ;) |
| 19:21.31 | stefan_schmidt | AndiM: For question about GPE phone I would re-route you to flo_lap |
| 19:21.34 | stefan_schmidt | hi flo_lap |
| 19:21.52 | AndiM | stefan_schmidt: good to know. |
| 19:22.01 | flo_lap | re |
| 19:22.22 | flo_lap | hi guys |
| 19:23.20 | AndiM | flo_lap: so, what are you contributing to the health of this project? ;)) |
| 19:23.26 | stefan_schmidt | flo_lap: How is GPE Phone ED progressing? |
| 19:23.41 | stefan_schmidt | flo_lap: Better then OM I hope ;) |
| 19:24.04 | flo_lap | AndiM: Mostly teaching the coders what do do :) |
| 19:24.22 | flo_lap | stefan_schmidt: currently not... unluckily :/ |
| 19:24.42 | flo_lap | stefan_schmidt: If you followed the news you might guess a conflict there |
| 19:25.31 | stefan_schmidt | flo_lap: No really. I learned in hard real life the difference between marketing and engineering |
| 19:26.10 | AndiM | flo_lap: ok, then please tell me why I cannot get any i2c communication interrupt going to my i2c amplifier :) (probably due to the i2c-based camera being powered off) |
| 19:28.17 | flo_lap | stefan_schmidt: that's a quite good start ;) in fact it is even more complicated... there are several levels of relations. |
| 19:29.58 | flo_lap | AndiM: hum well, i would start debugging this with a search for the logic analyzer ;) |
| 19:30.17 | AndiM | flo_lap: bzzzt, wrong answer ;) |
| 19:30.44 | flo_lap | hrm... darn |
| 19:31.07 | AndiM | let's hope I'll have an answer this evening. |
| 19:32.08 | stefan_schmidt | flo_lap: well, I need to find some ways around this "enlightments" |
| 19:32.30 | flo_lap | AndiM: ok, so you don't have something like this around... you could try to build one with a microcontroller and ram |
| 19:32.55 | flo_lap | stefan_schmidt: welcome to the club :) |
| 19:33.32 | stefan_schmidt | flo_lap: :) |
| 19:36.45 | stefan_schmidt | flo_lap: Ah, nice one. |
| 19:37.07 | stefan_schmidt | I'm just getting into low level eletronic stuff |
| 19:37.20 | stefan_schmidt | flo_lap: AVRs, PCBs and therelike |
| 19:37.55 | stefan_schmidt | flo_lap: Stealing some of alphaone skills ;) |
| 19:38.23 | alphaone | stefan_schmidt: Skillpirate! |
| 19:39.02 | stefan_schmidt | alphaone: How was your bike ride home? |
| 19:39.26 | flo_lap | hehe |
| 19:41.23 | AndiM | flo_lap: my father should have a semi-dozen MSOs in his lab... ;) |
| 19:41.54 | stefan_schmidt | AndiM: Well, something because you can visit him. |
| 19:42.21 | AndiM | alphaone: wow, that was some kind of rimshot! hours of idleness, then a very directed answer ;) |
| 19:42.56 | alphaone | stefan_schmidt: Was good. Less traffic than the ride there. |
| 19:43.23 | stefan_schmidt | alphaone: No surprise. Bike is still fine? |
| 19:44.08 | alphaone | stefan_schmidt: Sure |
| 19:44.17 | alphaone | AndiM: I have highlights |
| 19:44.44 | AndiM | alphaone: and I'm still using a rotten ircii ;) |
| 19:45.00 | alphaone | :-) |
| 19:51.19 | *** join/#openezx TimRiker (n=timr@70.1.43.26) |
| 20:30.21 | *** join/#openezx yansa (n=yans@host-89-167-37-237.pronet.lublin.pl) |
| 20:31.38 | AndiM | hi |
| 20:50.04 | *** join/#openezx tombhadAC (n=tombhad@pD95DED18.dip.t-dialin.net) |
| 21:05.46 | *** join/#openezx tombhadAC (n=tombhad@pD95DED18.dip.t-dialin.net) |
| 21:13.59 | *** join/#openezx BadCluster (n=badclust@200.26.114.37) |
| 21:20.04 | AndiM | i |
| 21:23.18 | AndiM | err... "hi"! |
| 21:28.48 | *** join/#openezx tombhadAC (n=tombhad@pD95DED18.dip.t-dialin.net) |
| 21:30.31 | AndiM | urks! looks like I've been hunting down the wrong i2c bus number all the time... |
| 21:31.30 | AndiM | now it seems to work, however I get a nice OOPS on mixer access. And before I also managed to get an i2c interrupt, but on this boot it didn't work. |
| 21:31.40 | AndiM | maybe it _is_ camera activation related after all... |
| 21:44.31 | *** join/#openezx tombhadAC (n=tombhad@pD95DED18.dip.t-dialin.net) |
| 22:10.26 | *** join/#openezx tombhadAC (n=tombhad@pD95DED18.dip.t-dialin.net) |
| 22:27.02 | AndiM | YAY! E680 amplifier does *something* |
| 22:28.00 | stefan_schmidt | AndiM: congrats |
| 22:28.29 | AndiM | at least i2c works, the controls work, and now let's see whether it actually works in a real-life kinda way ;) |
| 22:28.43 | AndiM | stooopid me ;) |
| 22:30.56 | AndiM | (I truly chose the wrong i2c bus) |
| 22:31.15 | AndiM | hmm, but so far I cannot see any real reaction of the controls. more testing... |
| 22:33.41 | AndiM | YES! had to activate Output Mixer AL and then choose the correct output device on device selector :) |
| 22:34.05 | AndiM | IOW, seems perfectly fine. |
| 22:38.43 | *** join/#openezx goxboxlive (n=goxboxli@134.84-48-212.nextgentel.com) |
| 22:39.35 | AndiM | goxboxlive: hi! greeting you with music ;) |
| 22:41.28 | goxboxlive | :-) hi |
| 22:42.50 | AndiM | goxboxlive: IOW: E680 amp works. |
| 22:43.13 | goxboxlive | ok |
| 22:43.31 | AndiM | I'll try to get it submitted this weekend. |
| 22:47.23 | stefan_schmidt | AndiM: Thanks, great work. |
| 22:48.04 | AndiM | stefan_schmidt: keep this for later when it's submitted and included ;) |
| 22:48.19 | stefan_schmidt | AndiM: heh :) |
| 23:01.57 | WM | AndiM: congrats!! :) |
| 23:03.14 | AndiM | WM: oh, another one :) |
| 23:05.50 | WyrM | AndiM: looking forward to test your code, are you going to send it to the ML this weekend? |
| 23:06.24 | AndiM | WM: that work was veeeeeerry difficult! Had to collect tons of pre-made LM4857-using drivers and pre-made LM4857 power-management patches and pre-made sound frameworks and pre-made Motorola phone frameworks. But the easiest part was stepping over my own incredible stupidity. Haha, just joking, I better won't tell the truth... |
| 23:07.13 | AndiM | WyrM: I'm definitely planning to. Either combined or in crude pieces, damnit! |
| 23:07.59 | WyrM | AndiM: hahaha, this happens, it took me over six months to figure that i need to configure the SSP3 pins to input to get communication on SSP2 :) |
| 23:08.17 | AndiM | WyrM: nice!! ;) |
| 23:09.06 | AndiM | WyrM: I think that's the most difficult issue: so many pins, so many registers, and so many combinations each... |
| 23:09.19 | WyrM | AndiM: and the camera?? got it to show up? |
| 23:09.45 | AndiM | WyrM: NOPE. not a blip. |
| 23:10.24 | WyrM | AndiM: have you tried to flip pcap VREG_V6? |
| 23:10.38 | AndiM | WyrM: but I have to admit that my hack was _VERY_ crude, just barely to be sure that clock initialisation is ok. |
| 23:11.07 | AndiM | WyrM: VREG_V6 _is_ activated by machine init, thus camera should be powered, right? |
| 23:11.33 | AndiM | or did I misunderstand those comments / bools? |
| 23:11.53 | AndiM | WyrM: but maybe that's the problem there after all... |
| 23:12.10 | AndiM | WyrM: 2.6.24 doesn't have any functional change from the Moto source in this aspect I think. |
| 23:12.48 | AndiM | (and we'd be stupid to do any major changes in the init code - nothing better than making a porting job even harder ;) |
| 23:12.50 | WyrM | AndiM: i really have no idea, i think that those registers configure some standby behaviour, and another pin is used to signal PCAP that AP is suspended. |
| 23:13.20 | AndiM | WyrM: yup, the comments make it sound as if it is just standby _configuration_, not actual level activation. |
| 23:14.54 | AndiM | WyrM: one thing I did was collect comments about all the PCAP registers & bits (from kernel and blob). That should hopefully make it easier to pinpoint further unknown PCAP I/Os. |
| 23:15.45 | WyrM | AndiM: it sure will! Have you added the information to the wiki? |
| 23:16.05 | AndiM | WyrM: nope, header. |
| 23:16.39 | AndiM | module description: "LM4857 FM amplifier (I2C)". ok? |
| 23:16.48 | WyrM | AndiM: perfect. |
| 23:17.52 | AndiM | or should I add "mixer driver" or some such? |
| 23:19.03 | WyrM | AndiM: the first is fine to me. :) |
| 23:20.39 | AndiM | WyrM: yeah, I think it's better to leave it shorter. |
| 23:20.40 | WyrM | AndiM: o know i am already abusing your good will, but it would be GREAT if you take a look on the GSM audio too! :) |
| 23:21.21 | AndiM | WyrM: that's a matter of audio _data_ routing between AP/BP etc., right? |
| 23:21.46 | WyrM | AndiM: it will probably be easier than the amplifier driver. |
| 23:21.53 | WyrM | AndiM: no, AP is not really involved. |
| 23:21.59 | AndiM | WyrM: one could say that this should have been the thing that I should have looked at first :-P |
| 23:22.03 | WyrM | it is direct BP <=> PCAP. |
| 23:22.34 | AndiM | oh, possibly even easier. then I should try to do it. |
| 23:22.53 | AndiM | WyrM: is there any easy test scenario? I wouldn't want to do a full GSM call ;) |
| 23:22.55 | WyrM | AndiM: i can give you raw PCAP registers values that makes it "kind of work". |
| 23:23.20 | AndiM | WyrM: but... but... but there is a nice magic function called "do entire audio routing for GSM" or so. |
| 23:23.49 | WyrM | AndiM: first you have to flash your phone, to get a boot with the BP not in flash mode. |
| 23:23.49 | AndiM | either in blob or kernel. I should be able to locate it again rather easily. |
| 23:23.58 | AndiM | WyrM: ah, right. |
| 23:24.14 | AndiM | WyrM: I wanted to do this anyway, to get a dual boot done. |
| 23:24.55 | WyrM | AndiM: yes, opening the Baseband PCM on our asoc driver _almost_ matches the registers on 2.4. |
| 23:25.58 | WyrM | let me look for some 2.4 dmesg when i dumped the registers values.. |
| 23:26.02 | WyrM | just a min. |
| 23:26.06 | AndiM | don't they have some kind of loopback mode to avoid GSM stuff? I thought there was something... |
| 23:26.39 | WyrM | loopback? i dont get what you mean... |
| 23:30.02 | WyrM | the values on the file were extracted from a 2.4 kernel, i could get GSM audio cheating the sound driver and directly writing the "on call" values to PCAP. |
| 23:32.40 | WyrM | about loopback.. everything sound related is connected together in network mode, so it is very flexible, you can, at least in theory, route the GSM audio to PCAP and at the same time read it on the AP. |
| 23:33.10 | AndiM | yeah, "network mode", that was the keyword. |
| 23:34.45 | WyrM | AndiM: i think DCC is not working for you; netcat wyrm.is.dreaming.org 31337 |
| 23:35.12 | *** join/#openezx TimRiker (n=timr@68-27-84-43.area1.spcsdns.net) |
| 23:35.22 | WyrM | all values dumped from 2.4 some time ago (from an a780). |
| 23:38.03 | flo_lap | good night |
| 23:38.08 | AndiM | WyrM: how do I get that file via netcat, do I need to do something? |
| 23:38.31 | WyrM | nc wyrm.is.dreaming.org 31337 > pcap_debug.txt |
| 23:39.36 | AndiM | ah, right, redirection. I _really_ should have used nc from time to time... |
| 23:40.44 | WyrM | :) |
| 23:40.46 | AndiM | WyrM: but that's just the log on the wiki ;) |
| 23:41.16 | WyrM | AndiM: it is? i think i neve sent it. Then just forget ;) |
| 23:41.24 | WyrM | s/neve/never/ |
| 23:41.44 | AndiM | WyrM: maybe not. it just seems similar. |
| 23:42.42 | AndiM | WyrM: can't we rename /proc/pcap VREG to AUXVREG, goddamnit? it's rather confusing otherwise... |
| 23:43.09 | AndiM | WyrM: already done locally, will just see the diff and remember to send a patch then. |
| 23:45.30 | WyrM | AndiM: sure, i dont really care about the naming ;) |
| 23:46.12 | WyrM | AndiM: and /proc/pcap will go away as soon as we have a 100% functional sound driver anyway. |
| 23:46.52 | AndiM | WyrM: is that a good idea? I'd think it should be left enabled for quite a while... |
| 23:47.55 | AndiM | WyrM: oh, my driver doesn't do any _active_ device probing, since I don't know characteristic register values of LM4857 currently (I'm just groking whichever i2c address people choose to probe with my driver). Should I implement this? |
| 23:49.37 | WyrM | AndiM: it will be useful to fully understand some other registers which are not accessible on a780/e680 (on a1200 the AP is connected to PCAP port1, on a780 port1 is connected to the BP). there are some registers to control battery charging, some more interrupts sources, etc.. |
| 23:49.58 | WyrM | but it is not really useful anymore on a780/e680. |
| 23:51.28 | WyrM | AndiM: no, no need to do any other probing. :) |
| 23:52.48 | AndiM | I'll do it anyway, since otherwise my driver might kill some hardware if people manage to misconfigure the address. |
| 23:53.25 | AndiM | some EEPROMs are said to get corrupted rather easily. |
| 23:54.35 | WyrM | AndiM: there are no other i2c hardware on e680 other than the camera.. Unless your driver is generic enough to be used on other boards i think it is not needed. |
| 23:54.48 | WyrM | but, of course, it is your decision :) |
| 23:55.40 | AndiM | BTW, the current driver is at ftp://lisas.de/~andi/temp_lm4857/ , if anyone cares ;) |
| 23:56.58 | AndiM | WyrM: damn sure it is! the driver was _supposed_ to be that, since Neo1973 should get updated to use it, and there might be more devices with LM4857 out there. all that's needed is an i2c_board_info at platform setup or so. |
| 23:58.40 | WyrM | AndiM: so, do it! I was thinking it was kind of specific to the e680. :) |
| 23:59.00 | WyrM | Could not chdir to ~andi: server said: Failed to change directory. |
| 23:59.27 | AndiM | WyrM: never ever code a specific driver! at least with a current 2.6.x doing so is a SIN... |
| 23:59.46 | AndiM | WyrM: errm, http of course, sorry. |