| 00:10.23 | *** join/#edev GPSFan (n=kenm@12.10.255.248) |
| 00:10.23 | *** mode/#edev [+o GPSFan] by ChanServ |
| 01:14.36 | *** join/#edev redblue (i=star@ppp050.109-253-207.mtl.mt.videotron.ca) |
| 02:44.31 | *** join/#edev T0mW (n=Tom@24.238.68.20.res-cmts.sth.ptd.net) |
| 02:44.56 | T0mW | hello |
| 05:55.21 | *** join/#edev casper__ (n=casper@S0106000f6630d670.gv.shawcable.net) |
| 07:01.48 | *** part/#edev casper__ (n=casper@S0106000f6630d670.gv.shawcable.net) |
| 10:03.04 | *** join/#edev tuxmaniac (n=aanjhan@unaffiliated/tuxmaniac) |
| 12:24.16 | *** join/#edev redblue (i=star@ppp087.109-253-207.mtl.mt.videotron.ca) |
| 12:48.29 | *** join/#edev prpplague (n=dave@69.73.203.189) |
| 12:59.23 | *** join/#edev GPSFan (n=kenm@12.10.255.248) |
| 12:59.23 | *** mode/#edev [+o GPSFan] by ChanServ |
| 13:18.51 | prpplague | it appears the wiki is working now |
| 13:23.31 | prpplague | i spoke too soon |
| 13:25.26 | prpplague | GPSFan: morning |
| 13:25.36 | *** mode/#edev [+o prpplague] by ChanServ |
| 13:26.58 | GPSFan | prpplague: yawn... morning.. |
| 13:32.37 | prpplague | GPSFan: whats cookin? |
| 13:33.46 | *** join/#edev dijenerate (n=dijenera@69.73.224.188) |
| 13:34.31 | prpplague | T0mW: ping |
| 13:34.39 | GPSFan | prpplague: .67" rain in 3 hours, stopped now... more or less. |
| 13:35.16 | dijenerate | hi all |
| 13:35.32 | dijenerate | GPSFan: where is this? |
| 13:36.14 | GPSFan | dijenerate: western colorado. |
| 13:36.22 | prpplague | dijenerate: morning |
| 13:36.27 | prpplague | GPSFan: lovely |
| 13:36.45 | prpplague | GPSFan: i miss the good old rain storms of east texas |
| 13:36.53 | dijenerate | prpplague: goodmorning |
| 13:36.53 | GPSFan | we needed the rain. |
| 13:37.07 | dijenerate | prpplague: how goes it? |
| 13:37.28 | dijenerate | GPSFan: |
| 13:37.41 | dijenerate | GPSFan: well you certainly got it |
| 13:37.48 | dijenerate | GPSFan: no flooding I hope? |
| 13:38.08 | prpplague | dijenerate: it goes |
| 13:38.13 | GPSFan | dijenerate: indeed, must be careful what we wish for... |
| 13:38.49 | GPSFan | dijenerate: not yet, high country got a bit more, gotta check the ditches after breakfast. |
| 13:39.44 | dijenerate | GPSFan: Florida got a knocking this week as well, but the last thing they need is to wish for bad weather |
| 13:40.42 | dijenerate | well, I'll be back in a couple of hours you guys, gotta get my sleep when I can and this is my first Lazy Sunday in months |
| 13:42.03 | GPSFan | dijenerate: pleasant dreams ;>) |
| 13:47.19 | T0mW | prpplague: pong |
| 13:48.25 | prpplague | T0mW: hey |
| 13:48.31 | prpplague | T0mW: guestion on p-channel mosfet |
| 13:48.40 | prpplague | T0mW: one of my schematics shows a BSS84 |
| 13:48.46 | prpplague | T0mW: which is a surface mount |
| 13:48.55 | prpplague | T0mW: think i could just swap that with a BS250? |
| 13:49.01 | T0mW | prpplague: hoo boy! now I am reaching the limit of what I know |
| 13:50.09 | prpplague | hehe |
| 13:50.12 | T0mW | prpplague: I couldn't say Dave. |
| 13:50.39 | prpplague | T0mW: wow |
| 13:50.54 | prpplague | T0mW: i asked you something electronics related and you couldn't answer, wow |
| 13:50.55 | prpplague | :D |
| 13:51.21 | T0mW | prpplague: depends on a lot of factors in how the device is being used: current, voltage, etc. Best to look over the data sheet on the new device and look to see if where it is going will violate any of it's specs. |
| 13:52.17 | T0mW | prpplague: but, for me, if it cannot use a 2N7000, then I'm in trouble |
| 13:56.02 | prpplague | hmm |
| 13:56.41 | prpplague | T0mW: basically its just using the bss84 to latch some data on some gpio's during the initial power up sequence |
| 13:56.47 | prpplague | the specs look similiar |
| 13:57.04 | T0mW | prpplague: your basic enhancement mode NFET, works very nicely as GP switch @ 5volt logic |
| 13:57.18 | T0mW | 200ma output |
| 13:57.41 | prpplague | T0mW: ahh, this is a 3.3v item |
| 13:57.49 | T0mW | prpplague: good relay driver as I also has a diode across the source + drain |
| 13:58.04 | T0mW | s/I also/it also |
| 13:58.51 | prpplague | T0mW: basically what this does is when the system's reset is low its latching the data onto a gpio, and when the reset goes high, then on the trailing edge to unlatches the data |
| 13:58.52 | T0mW | prpplague: yeah, figured that. I had to go through a session of looking for a new 3.3v replacement for the old 2N7000 reliable |
| 13:59.38 | prpplague | T0mW: ok well i'll just have to give it a try |
| 13:59.48 | prpplague | T0mW: oh one more question |
| 13:59.51 | prpplague | T0mW: on eagle |
| 14:00.17 | prpplague | T0mW: doing the board layout, setting the dimensions of the board is just doing a wire on the dimensions level with a 0 width right? |
| 14:00.19 | T0mW | prpplague: yeah, prolly applying a signal to a pin coming out of reset, but they also wanted to use the pin as GPIO? Is there a cap involved? |
| 14:00.35 | prpplague | T0mW: exactly, no cap listed |
| 14:00.48 | T0mW | prpplague: correct, the dimension is a wire on its own special layer |
| 14:02.04 | T0mW | prpplague: I finally decided on a new NFET ehancement mode, but the part number looks like something they paint on airplanes: 10 digits long |
| 14:02.58 | T0mW | MGSF1N03LT1 |
| 14:02.59 | T0mW | bah |
| 14:03.04 | T0mW | heh |
| 14:03.27 | T0mW | prpplague: heh, long number but it works ok |
| 14:04.27 | T0mW | GPSFan: ping |
| 14:06.51 | prpplague | T0mW: yea, i need something thats through hole |
| 14:07.24 | prpplague | hehe |
| 14:08.00 | prpplague | T0mW: all the bread i had has gone moldy, so my hot dogs i use tortillas |
| 14:08.49 | T0mW | prpplague: ah, well, most any device will do ya. just look at the specs: Vds (max voltage on output), Ids (max output current), VgsON (on voltage), VgsOFF (when it turns off) |
| 14:08.49 | prpplague | T0mW: oh, one more eagle question |
| 14:09.05 | prpplague | T0mW: yea, thats what i figured |
| 14:09.10 | *** join/#edev tuxmaniac (n=aanjhan@unaffiliated/tuxmaniac) |
| 14:09.20 | prpplague | just didn't have much experience with p-channel mosfets |
| 14:10.00 | prpplague | T0mW: if you do an electrical change on your board, does it update the schematic or is it schematic-> layout only? |
| 14:10.01 | T0mW | prpplague: then, look for the graphs on the device, the performance graphs can help you locate the conditions you are going to use it under and how it is to perform |
| 14:11.46 | T0mW | prpplague: well, if you pinswap in the layout, it will move the connection on the schematic. but normally, you go from the schematic to the board direction. I don't pinswap as most packages do the swapping differently. Some packages relabel the pins / names on the device in the schematic, others will actually move wires |
| 14:12.15 | T0mW | pcb layout reflects the changes in the schematic is how I work it. |
| 14:13.16 | T0mW | prpplague: one thing you do want to do is to run the ERC (electrical rules check) and the DRC (design rules check). |
| 14:13.29 | prpplague | T0mW: mainly what i was looking to do is layout a few connection points on the board first, then do the schematic to connect them |
| 14:14.11 | prpplague | T0mW: yea, i'm using the default settings for erc and drc, but i get a warning about the via's drill size |
| 14:14.17 | T0mW | prpplague: ERC does two things: it checks the way you described the part in the library against how you wire it electrically to other parts: e.g. you don't wire an output to a power pin. |
| 14:15.00 | T0mW | prpplague: ERC also checks the PCB to make sure that what is on the board wiring is what is shown in the schematic. it is a way of keeping both into sync |
| 14:16.08 | prpplague | T0mW: right |
| 14:16.08 | T0mW | prpplague: there are people who layout boards who don't bother to use the netlist (description of pcb pin wiring networks). I've seen boards where the schematic did not jive with how the pcb was actually wired. |
| 14:16.32 | prpplague | interesting |
| 14:16.56 | prpplague | i guess it would be better to do a part then with all the holes i need |
| 14:17.50 | T0mW | prpplague: DRC checks to see that you follow the physical rules you decided upon. You can customize the DRC settings as to how close various objects are to each other: pin to pin, track to pin, track to track, track to edge of board, track to via, etc. |
| 14:18.03 | prpplague | T0mW: you prefer to use all right angle turns or more of the / or \ turns? |
| 14:19.00 | T0mW | prpplague: the DRC keeps you within the limit of what your pcb house can do. Some pcb houses can do 10mil seperation, others do 8mil, and still others do 6mil. You can get even finer resolution, but the closer you put things, the higher the manufacturing costs. |
| 14:19.24 | prpplague | yea i figured as much |
| 14:19.44 | T0mW | prpplague: that is mostly personal preference, I prefer 45 degree angles, my preference, but I don't follow that as a rigid rule |
| 14:20.00 | T0mW | prpplague: keep in mind, they call the copper stuff: artwork |
| 14:20.08 | T0mW | prpplague: that is because it is. |
| 14:20.44 | T0mW | prpplague: one of the most sucessfull PCB designers I ever worked with was a women who knew little about electricity. |
| 14:21.16 | T0mW | prpplague: once I asked her how she did such great boards, she told me that she just did it so it "looked pretty". |
| 14:21.46 | T0mW | prpplague: her boards I had very little / no problem with cross-talk or noice |
| 14:21.53 | T0mW | s/noice/noise/ |
| 14:22.11 | prpplague | T0mW: yea |
| 14:22.20 | T0mW | prpplague: so, make them "pretty" |
| 14:22.24 | prpplague | T0mW: our layout guy doesn't know alot about electronics either |
| 14:23.09 | T0mW | prpplague: they really don't have to. But they have to know that you don't take all the supply bypass caps and lump them into one area of the board! |
| 14:23.26 | prpplague | hehe yea |
| 14:23.34 | T0mW | prpplague: btdt! |
| 14:23.46 | prpplague | hehe |
| 14:24.29 | T0mW | prpplague: btw, you can build a board an violate all the rules in eagle: DRC & ERC. |
| 14:24.30 | prpplague | T0mW: been trying to think of a good removable socket to use for the bus interface |
| 14:24.41 | T0mW | prpplague: ha |
| 14:24.53 | prpplague | T0mW: but all i keep coming up with is a the cf socket |
| 14:25.11 | T0mW | prpplague: several types of sockets came to mind while wonder what you meant by "bus interface" |
| 14:33.33 | chouimat | morning |
| 14:45.58 | prpplague | chouimat: morning |
| 15:03.31 | GPSFan | T0mW: pong |
| 15:03.39 | prpplague | http://www.surpluscomputers.com/store/main.aspx?p=ItemDetail&item=TOL10275 |
| 15:03.46 | prpplague | recon those are any good? |
| 15:06.46 | GPSFan | prpplague: there are 2 kinds of el'cheapo calipers, .005 res & .0005 res. seem to be about the same price too, I got a .0005 res one from Harbor Freight, and it's fine, except it eats batteries. |
| 15:07.11 | GPSFan | that's inchs btw. |
| 15:07.47 | T0mW | GPSFan: OH! just the man I was hoping to find |
| 15:08.13 | T0mW | GPSFan: I got everything building clean now, thanks to the km8 patches |
| 15:08.20 | GPSFan | ;>) |
| 15:08.37 | T0mW | heh |
| 15:08.43 | GPSFan | ack.. |
| 15:09.07 | GPSFan | T0mW: ok, thats good, can I get a tarball sometime? |
| 15:09.17 | T0mW | GPSFan: I took the aeronix patches and yours and broke them out into individual files so that some one else can move off 2.4.21 |
| 15:09.26 | T0mW | now |
| 15:09.29 | GPSFan | swell |
| 15:09.48 | T0mW | two things are not working, maybe three: wifi, sound and switch_root |
| 15:09.57 | T0mW | the sound I haven't tried |
| 15:10.10 | T0mW | but, is the wifi in your patches? |
| 15:10.11 | GPSFan | does the wifi driver load? |
| 15:10.32 | GPSFan | it's a module |
| 15:10.43 | T0mW | GPSFan: I see a non-amatuer radio in the ethernet for the kernel and it is activated, but no device selected |
| 15:10.58 | T0mW | nothing checked off |
| 15:11.18 | T0mW | no module is built |
| 15:11.31 | GPSFan | that was for the ep7312 eval board that had a CS8??? ehternet chip. I thought I disabled that.. |
| 15:11.51 | GPSFan | the wifi module is from aeronix, we can't rebuild it. |
| 15:12.03 | T0mW | shit, it is binary? |
| 15:12.11 | GPSFan | yeeeesss |
| 15:12.15 | T0mW | aw |
| 15:12.30 | T0mW | well, looks like we are married to 2.4.21 then |
| 15:12.52 | GPSFan | I never got around to porting their "patches" to the non released source code to the latest GPL'd source for the wifi. |
| 15:13.16 | GPSFan | that's all that's holding up a move to a newer kernel. |
| 15:13.17 | T0mW | GPSFan: oh, so it would be possible to make a wifi driver source? |
| 15:14.09 | T0mW | GPSFan: ok, this is the plan, once I get a build system together and ready for release, I would like it posted on Yahoo files? |
| 15:14.21 | T0mW | rather than any site of mine |
| 15:14.26 | GPSFan | read their note at the bottom of this page.. http://www.zipitwireless.com/linux.html |
| 15:15.08 | T0mW | hmm |
| 15:15.20 | GPSFan | T0mW: only problem with posting it to Yahoo is there ain't any room left there. that's why there are no kernel sources there. |
| 15:15.24 | T0mW | well, I guess I should be happy with what I do have then |
| 15:15.34 | GPSFan | be happy! |
| 15:15.43 | T0mW | GPSFan: can you delete the old buildroot and post the new one? |
| 15:15.58 | GPSFan | <PROTECTED> |
| 15:16.38 | T0mW | well, I am only taking this as far as building a 2.4.21, someone else may take it further. |
| 15:16.44 | GPSFan | T0mW: what I'd likle to do is move all the sources, etc off yahoo, maybe to the elinux wiki, |
| 15:16.52 | T0mW | GPSFan: yes |
| 15:17.23 | T0mW | GPSFan: just have a README-stuff-is-on-elinux |
| 15:17.37 | GPSFan | that's fine. I just haven't had time to do it. I was hoping for more kernel level hacking from the community, but no such luck. |
| 15:18.10 | T0mW | GPSFan: what I'd like to do is wipe all the buildroot / compile stuff off elinux and replace it with a single page for the new buildroot. |
| 15:18.23 | T0mW | GPSFan: the info on the elinux is incomplete and confusing |
| 15:18.26 | GPSFan | sounds good to me, |
| 15:19.02 | GPSFan | in fact so is the sruff on yahoo. a re-do of elinux would be a boon to the zipit. |
| 15:19.12 | T0mW | GPSFan: ok, that is a plan then. I'll finish up the buildroot. |
| 15:19.45 | T0mW | it is not really a buildroot, but I started with that. buildroot is too bloated and convoluted to get it to build a code system correctly |
| 15:20.12 | GPSFan | sort of like what openWRT did, maybe? |
| 15:20.41 | chouimat | GPSFan: buildroot-ng? |
| 15:20.57 | T0mW | I had to segregate devices from targets so that the linux modules and user skeleton would be properly added into the resulting rootfs image |
| 15:21.16 | GPSFan | chouimat: kinda like that.. |
| 15:21.49 | T0mW | chouimat: is is too tightly bound together to assert control over how the whole process proceeds |
| 15:21.51 | chouimat | GPSFan: I'm trying to understand how it work ... they didn't document the changes |
| 15:22.45 | T0mW | for example, the filesystem make is included into TARGETS, it builds as a TARGET and the rootfs is built before you build the zimage |
| 15:22.55 | chouimat | T0mW: I was toying with cmake lately ... since kde is using it for kde4 why not using it to build firmware :) |
| 15:23.04 | GPSFan | chouimat: nobody seems to document anything about buildroot, they just say RTFS.. not the best of ways to develop. |
| 15:23.04 | T0mW | problem is that the kernel I have has modules that need to be installed into the rootfs |
| 15:23.36 | T0mW | so, I split out the filesystem build as ROOT_FILESYSTEM and added that after TARGETS |
| 15:24.35 | prpplague | T0mW: how do you do the distance measurement in eagle again? |
| 15:24.41 | GPSFan | T0mW: I know what you mean, to build openzipit, there is the kernel, the rootfs which is mostly busybox, and the apps, some of which are built with buildroot and some not. That's mostly 'cause I couldn't make some of the apps build under buildroot, or the kernel. |
| 15:24.44 | chouimat | GPSFan: I agree ... and oe support for the wrt54 seems to be inexistant ... and every time I try to get a 8mb image for my wrtsl54gs it buildroot also produce the 4mb one and complain about the fact it's too big to fit in 4mb ... and they are not helpfull in their irc channel |
| 15:24.44 | T0mW | prpplague: set a mark |
| 15:24.57 | T0mW | prpplague: 'mark' icon |
| 15:25.18 | T0mW | prpplague: choose 'mark' then click to place the mark. |
| 15:25.51 | T0mW | prpplague: a new measurement dial will appear to the left of the command line |
| 15:26.10 | prpplague | hmm |
| 15:26.24 | prpplague | i'm not seeing anything called "mark" |
| 15:26.26 | prpplague | this is in the board layout section? |
| 15:26.38 | prpplague | nm |
| 15:26.40 | prpplague | found ti |
| 15:26.41 | T0mW | chouimat: yeah, you really have to delete the main Makefile, then start putting your own together using the original as a guide |
| 15:27.52 | chouimat | T0mW: or I will get so much pissed off that I will simply port gentoo to it or use www.t2-project.org instead :) |
| 15:28.02 | T0mW | lol |
| 15:28.08 | prpplague | hmm |
| 15:28.27 | chouimat | T0mW: using t2 I can build an image for my dreamcast :) |
| 15:28.47 | prpplague | T0mW: that suppose to give you the distance between two marks? |
| 15:28.56 | prpplague | T0mW: or between the mark and an object? |
| 15:29.37 | T0mW | prpplague: no, it sets the relative origin, then when you move the cursor away from that origin, it give the distance (dynamically, not static) |
| 15:30.23 | T0mW | prpplague: the distance is rounded to the grid units. so, if you have a 25mil grid, all distances are rounded to 25mil |
| 15:31.23 | prpplague | ahh ok, gotcha |
| 15:32.54 | T0mW | GPSFan: wlags49_h25_cs.o is the wifi module? |
| 15:33.23 | GPSFan | yep |
| 15:35.52 | prpplague | GPSFan / T0mW what do you guys think about using a CF card socket as a removable socket for the pixter? |
| 15:36.24 | prpplague | CF card isn't exactly the friendliest hobby board |
| 15:36.32 | T0mW | you mean to plug in the pixter to something else? |
| 15:36.58 | prpplague | T0mW: the pixter uses a cardedge connector for their cartridges but those would be really hard to make |
| 15:37.19 | prpplague | T0mW: i was trying to think of some other cartridge interface |
| 15:37.44 | T0mW | prpplague: how many pins does it need? |
| 15:37.55 | GPSFan | prpplague: if there are enough pins, and you can get both ends, go for it. |
| 15:42.04 | T0mW | GPSFan: bleah! the wifi driver dumps a lot of debug crap |
| 15:42.15 | T0mW | dmesg |
| 15:42.16 | T0mW | stuff |
| 15:43.18 | T0mW | ok, got wifi |
| 15:46.32 | GPSFan | T0mW: the wifi driver dumps "tons" of debug info, I think it was never re-compiled to remove their defvelopment debug code. |
| 15:47.30 | T0mW | GPSFan: it is like their patch file, they didn't cleanup the old sources: *.bak, *.orig, *.old |
| 15:47.44 | T0mW | they just dumped everything |
| 15:48.00 | T0mW | GPSFan: I guess we pissed them off? |
| 15:48.01 | GPSFan | T0mW: maybe the guy working on it left "quickly" |
| 15:48.05 | T0mW | LOL |
| 15:48.30 | T0mW | GPSFan: probably a traveling kernel guru, got his paycheck and ran |
| 15:48.53 | GPSFan | yeah, their promise to provide a new gpl'd wifi driver is as old as that page. the recest "opt-out" note is the first update in years. |
| 15:49.40 | T0mW | GPSFan: well, at least we will have a fairly decent surplus unit to play with. Eventaully it will sell on ebay for < $20 |
| 15:49.51 | T0mW | chouimat: $20 is good |
| 15:49.52 | T0mW | heh |
| 15:50.12 | GPSFan | chouimat: it was a great learning experience for me, it was worth it to me. |
| 15:50.36 | T0mW | GPSFan: I am planning to use one of these units as a data capture device. Send it out in the field with an RS232 connenctor on it, hook it into systems and leave it there a few days. |
| 15:51.06 | T0mW | GPSFan: simple menu to set baudrate, then echo the data onto the LCD to verify it is working correctly |
| 15:51.22 | chouimat | ok ... anyway I will wait sometimes need to get a new job (contract) first ... I'm currently leaving on my "safety marging" ... |
| 15:51.49 | T0mW | chouimat: yeah, my margin is getting thin too |
| 15:51.49 | GPSFan | T0mW: that's like my weather station controller, http://www.paonia.com/~kenm/Pix/?display=images/Zipit/Weather/pict1442.jpg&width=800&height=600 |
| 15:51.49 | chouimat | errr living ... can't type today :( |
| 15:52.18 | T0mW | GPSFan: exactly, an inexpensive device running linux |
| 15:52.43 | T0mW | I need to get openvpn working next |
| 15:52.49 | GPSFan | it had a 9 month uptime when the LT ldo regulator took a crap.. |
| 15:53.43 | chouimat | T0mW: 4 weeks ago one of my friend asked me for nice update to the firewall I build for him ... he probably sold 15 units to a huge co ... the problems is 3 days after the call he got hospitalised for burn out and severe internal shutdown ... so I think that this 20K is on the "would have been nice to have" :( |
| 15:53.59 | T0mW | GPSFan: I wonder if you had a lightning strike in your area, this induced a spike into the A/C power cord and in turn spiked that regulator? |
| 15:54.29 | T0mW | chouimat: not good |
| 15:54.48 | GPSFan | T0mW: no AC, it's solar powered, and I thought of that too, it's possible, but I would have thought that other stuff would have been fried too. |
| 15:55.22 | T0mW | GPSFan: ok |
| 15:57.00 | GPSFan | T0mW: could have been heat related, it was hot during that time, and the ldo is a weeny little part with no heatsinking. |
| 15:58.34 | chouimat | T0mW:I just hope he will get better soon ... |
| 15:59.35 | T0mW | GPSFan: what is iwconfig? is that busybox? |
| 15:59.58 | GPSFan | T0mW: it's in wireless tools. |
| 16:00.13 | chouimat | LOL "If you don't care where you are,then you ain't lost" <---- QOTD |
| 16:00.18 | GPSFan | iwconfig, iwlist, iwpriv... |
| 16:02.18 | GPSFan | T0mW: iwconfig configures the wireless aspects of the wifi interface, used with ifconfig to complete the network configuration. |
| 16:10.32 | T0mW | GPSFan: I don't think that aeronix has a copyright on that bootloader. It is too well written for them to have done it. It checks the SDRAM to see if it is a 32bit wide data path, no need to do that. I would think that a generic loader was used |
| 16:13.17 | GPSFan | T0mW: compared to their patch, I'd have to agree. but there is no real way to tell. |
| 16:13.49 | T0mW | that printk stuff in the wifi driver is a real wart |
| 16:15.02 | GPSFan | T0mW: on the Zipit you must check the path width, 'cause it can be 16 or 32. the wifi driver patch is a real hack on pcmcia-cs too. |
| 16:15.37 | T0mW | the SDRAM is either 16 or 32bit?! |
| 16:15.39 | GPSFan | T0mW: that is the ep7312 supports both 16 or 32 bit wide mem |
| 16:16.13 | T0mW | ep7312 does, but I though the SDRAM in the ZipIt was only 16bit bus |
| 16:16.41 | GPSFan | I think the ep7312 eval bd is 32 and I bet that's what they did ther development on |
| 16:16.57 | GPSFan | so the code had to wrok on both. |
| 16:17.06 | T0mW | yeah, considering they trashed the JTAG port on the production unit... |
| 16:17.23 | GPSFan | and the serial ports. |
| 16:17.35 | T0mW | I just love the teensy mental mindset of some of these people |
| 16:17.46 | GPSFan | luckely the layout guy was lazy. |
| 16:17.50 | T0mW | their view of the world is so narrow |
| 16:18.28 | T0mW | :P |
| 16:19.35 | T0mW | we had a new housing development go up in the back here, now you have all new smells: bacon and coffee in the morning |
| 16:19.44 | T0mW | right now I smell tuna fish |
| 16:19.44 | GPSFan | T0mW: just think of what the Zipit II could have been, EP9312, color screen, sd/mmc card 802.11G, stereo in/out. same size, $199. |
| 16:19.53 | T0mW | oh yeah |
| 16:38.04 | *** join/#edev tuxmaniac (n=aanjhan@unaffiliated/tuxmaniac) |
| 17:05.41 | *** join/#edev tuxmaniac (n=aanjhan@unaffiliated/tuxmaniac) |
| 17:25.57 | *** join/#edev prpplague (n=dave@69.73.203.189) |
| 18:09.31 | *** join/#edev sunrunner20 (n=jamesdoe@pool-71-252-248-36.dllstx.fios.verizon.net) |
| 18:13.22 | *** join/#edev Anzur (n=Anzur@host-81-191-61-25.bluecom.no) |
| 18:13.32 | *** part/#edev Anzur (n=Anzur@host-81-191-61-25.bluecom.no) |
| 18:50.43 | *** join/#edev tuxmaniac (n=aanjhan@unaffiliated/tuxmaniac) |
| 19:23.23 | *** join/#edev EvilDevil_ (n=miau@p54A6FF24.dip.t-dialin.net) |
| 19:53.16 | *** join/#edev bd2 (n=ufo@81.222.177.146) |
| 22:17.35 | *** join/#edev elvueno (n=elvueno@84-120-211-7.onocable.ono.com) |
| 23:48.54 | *** join/#edev agaffney (n=agaffney@gentoo/developer/pdpc.active.agaffney) |
