| 08:51:24 | seletz | hi |
| 09:29:15 | Sammy | hello seletz |
| 13:42:36 | seletz | erikm: hi |
| 13:50:48 | erikm | hello |
| 15:10:38 | prpplague | morning friends |
| 15:10:50 | prpplague | hope everyone is having a good day of coding.... |
| 15:21:48 | seletz | prpplague: hi, yes i have, specially now as pcmcia works :) |
| 15:22:04 | erikm | plays with bk again |
| 15:22:40 | erikm | once you get the trick it actually works nice |
| 15:23:19 | seletz | erikm: what disturbs me is that the source dirs only get populated when issuing "bk edit". What about make? |
| 15:23:42 | prpplague | seletz: whooaaa, pcmcia working thats great |
| 15:24:31 | prpplague | erikm: not you too! your slipping into the dark side ( bk that is!) |
| 15:24:44 | prpplague | seletz: so when do i get a sample board? |
| 15:25:11 | seletz | prpplague: yes. Couple of silly errors introduced & removed by me _and_ 2.5.2 irq code did the trick :) |
| 15:25:33 | erikm | seletz: try bk co |
| 15:25:40 | erikm | seletz: or better: bk -r co |
| 15:26:16 | erikm | prpplague: bk is not the dark side |
| 15:26:44 | prpplague | erikm: lol, i'm just kidding around |
| 15:27:31 | seletz | prpplague: well, thats not up to me anymore. Now i'm having a development contract with pruftechnik, but i think the'll push out OEM boards as soon as the handheld measurement device is out. |
| 15:28:49 | seletz | has to RTFM the bk manual .... :) |
| 15:29:07 | erikm | seletz: jgarzik is preparing a nice manual |
| 15:29:30 | erikm | seletz: well, one that describes how to work with kernel repositories |
| 15:30:04 | seletz | erikm: you said that. We're thinking about moving from CVS to bk for all SW projects, and to move the old CVS projects to bk. |
| 15:31:08 | prpplague | is bk that much easier to use when managing projects? |
| 15:32:05 | seletz | prpplague: i think for me the main benefits are beeing able to rename files and to take the work with you anywhere (with the ability to do ci), and to have changesets. |
| 15:33:41 | seletz | prpplague: having a "disconnected" sort of repository is one thing i really need. Now we do use scripts which rsync the work made at home. That's pretty ugly. |
| 15:34:00 | erikm | seletz: yes, the "multiple repositories" thing is pretty neat |
| 15:34:54 | erikm | right now I'm testing bk together with rmk: I cloned linus's 2.5 tree and made two local clones: arm-2.5 and net-drivers-2.5 |
| 15:35:23 | seletz | ah? |
| 15:35:57 | erikm | I pulled rmk's updates in the arm-2.5 repository, and the net-driver updates from jgarzik's net-driver-2.5 repository |
| 15:36:20 | seletz | Well, i want to generate the lnext patches using CVS/diff (old way:), the patches that follow i'd rather create with bk. Is that reasonable? |
| 15:37:13 | erikm | I'm developing the cs89x0 driver in my local net-driver-2.5 repository. I have a "hacking tree" that I cloned from linus tree, and from which I pull from both the local clones of arm-2.5 and net-drivers-2.5 |
| 15:37:22 | prpplague | is in the stone ages... still using tarballs with dated names |
| 15:38:08 | erikm | seletz: yes, bk can generate diff -u patches |
| 15:39:02 | seletz | ok, basically what one needs to do is: clone a vanilla kernel, pull russells patches into it, hack and use bk to create diffs? |
| 15:39:54 | erikm | you probably want both a local clone of linus's tree and rmk's tree |
| 15:40:34 | erikm | and because clone has the "-l" option (create hard links), having an extra repository doesn't cost much disk space |
| 15:41:24 | erikm | (except that rmk's tree is not yet publically available, I'm pulling from his home machine over an adsl line) |
| 15:42:11 | seletz | erikm: ok, the usual question to follow :) |
| 15:42:33 | seletz | erikm: Do you know when it will be available? |
| 15:42:39 | erikm | seletz: no |
| 15:42:42 | seletz | :) |
| 15:43:36 | erikm | we're just playing with it, to see if and how it works |
| 15:43:47 | seletz | ok, np. |
| 15:44:12 | seletz | getting smc9194 to work with 2.5.2-rmk6 |
| 16:02:48 | seletz | Argh! -ing CONFIG_ISA |
| 16:03:06 | erikm | huh? |
| 16:04:05 | seletz | well, there's a #elif defined(CONFIG_ISA) in smc9194.c which tricked me a bit. |
| 16:05:49 | seletz | erikm: #ifdef defined(neponset) #elif defined(isa) #elif defined(system3) #endif does not work as expected. |
| 16:06:03 | seletz | erikm: have to move up system3 ... |
| 16:06:06 | erikm | you mean #ifdef CONFIG_SA1100 |
| 16:06:26 | seletz | looking again |
| 16:06:38 | erikm | and if you really want to make it clean, you'd better have the #ifdef hell in a separate header file |
| 16:07:25 | seletz | erikm: no, it's really CONFIG_ISA |
| 16:07:48 | seletz | erikm: and this CONFIG_IAS is meant for ISA bus .... |
| 16:09:08 | seletz | erikm: should i move the arch dep init code out in separate functions and define them in the header? |
| 16:09:19 | prpplague | seletz: ya i had lots of problems with the config_isa |
| 16:09:41 | erikm | seletz: that usually makes the stuff a lot cleaner |
| 16:09:41 | seletz | erikm: like: #define smc_arch_init() smc_system3_init() |
| 16:10:08 | seletz | erikm: and do #ifdefs in the header file for smc_neponset_init() smc_isabus_init() etc |
| 16:10:20 | erikm | *nod* |
| 16:10:24 | seletz | ok |
| 16:10:26 | seletz | will do |
| 16:10:43 | seletz | hopes rmk will accept the patch ;^) |
| 16:10:45 | erikm | just an idea, but it makes the actual driver code a lot easier to read |
| 16:10:55 | seletz | agreed |
| 16:10:56 | erikm | who is the author? |
| 16:11:03 | seletz | looks |
| 16:11:22 | seletz | erik stahlman |
| 16:11:56 | erikm | hmm, not sure if he is still alive |
| 16:12:07 | erikm | (alive as in: still maintaining it) |
| 16:12:13 | seletz | last entry is from 96 |
| 16:12:20 | seletz | looks |
| 16:12:55 | seletz | no stahlman in MAINTAINERS |
| 16:14:09 | seletz | well, i guess i'll just make the change, send a patch to linux-arm-kernel and wait for reactions |
| 16:30:36 | prpplague | erikm: btw, you got blob running on the ipaq yet? |
| 16:34:23 | seletz | erikm: hmm, where do the actual functions go? smc_your_arch_init()? headerfile or source? |
| 16:41:25 | erikm | seletz: ask jgarzik, he might know the maintainer |
| 16:41:34 | erikm | seletz: or first try to mail the maintainer |
| 16:41:40 | erikm | prpplague: no, sorry -ENOTIME |
| 16:41:58 | seletz | erikm: ok, thx |
| 16:42:06 | prpplague | erikm: bummer |
| 16:43:36 | erikm | looks at lilo's global message |
| 16:43:48 | erikm | hmm, I might want to give a talk about blob on OLS |
| 16:45:46 | prpplague | erikm: guess its no loss, i'm not real impressed with the ipaq |
| 18:02:47 | seletz | erikm: Does this mean to you anything? "Bad mode in prefetch abort handler detected: mode UK4_26" |
| 18:04:17 | erikm | not, not really |
| 18:04:57 | seletz | argh. all of a sudden my kernel doesn't even boot. GRRR |
| 18:06:51 | seletz | ah, my socket_state() func oopses. hmm |
| 18:07:12 | erikm | goes skating |
| 18:07:13 | erikm | bye |
| 18:07:22 | seletz | have fun :) |
| 19:16:47 | prpplague | howdy there akira|afk |
| 19:18:07 | akira | howdy :) |
| 19:19:20 | akira | did seletz solve his kernel panic ? :) |
| 19:35:58 | prpplague | akira: ya i think he got the pcmcia stuff working under a 2.5 kernel |
| 19:42:34 | akira | oh good :) then i'll have a happy boss tomorrow :> |