Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - wsuetholz

Pages: 1 2 [3] 4 5
31
Zaurus - pdaXrom / Beta4 Hostap Packages.
« on: August 16, 2006, 04:04:59 pm »
Since nobody responded..  I have now tried beta 3, and most of the things needed are there, including code in the hostap scripts to properly handle the reloading of the firmware on a suspend/resume transition.  It was missing the firmware files, but that wasn't so hard to get/find.  

So, the hostap stuff for this card, works in beta3, and doesn't work in beta4.

Bill

32
PocketPenguin / Words Of Encouragement And Some Questions
« on: August 16, 2006, 12:14:43 pm »
Quote
do you now how hard it is to get a screwdriver on a plane these days, you Oldies back in the good old days had it easy. now days we have to go on 20 hour trips with no gadgets and we enjoy it!!

[div align=\"right\"][a href=\"index.php?act=findpost&pid=138680\"][{POST_SNAPBACK}][/a][/div]

The next thing will be banning even the plastic styluses from airplanes.  Not to mention after market ones like the Pilot Pentopia.

Bill

33
PocketPenguin / Body Design
« on: August 16, 2006, 12:06:45 pm »
I don't know if I can explain this properly, but...

How about a USB connector that is parallel to the bottom of the case covered by a spring loaded cover that the addon would push down on to make the connection..  The connector on the main body would be recessed.

Bill

34
Angstrom & OpenZaurus / 3.5.4.1 On Borzoi Using Akita Packages
« on: August 15, 2006, 01:27:08 am »
The Cacko release does indeed use the utilities to resize the flash partitioning..  They recommend a minimum of 32 meg for root.  Because of lack of source code for some of the drivers and things in the 2.4 kernel, it wouldn't be a very good idea to do a Cacko with a 2.6 kernel, right?

adf, the C1000 flash is the same as C3100 and C3200, don't you mean the C3000?

Koen, I tried the ipkg install with the -o, and it gave me errors indicating that the packages couldn't be found, when I removed the -o, it found them ok...  Besides which if the -o worked, I think from what I've been reading, that the ipkg-link wouldn't work properly for the task type installs, since it doesn't do dependencies (from what I infer).

Like I said, I'm fairly new to the Z, and I'm still trying to decide on the best ROM for my needs.  I like the look and feel of OPIE, but I need rdesktop and vnc..  I tried gpe, but there were issues with some of the configuration programs not saving the configs.  Mostly date/time, and wireless networking.

I also tried the latest pdaXrom, but, didn't like replacing the flash bootloader, and my CF Prism3 based wireless card refused to work, and I got no responses to my request for help.

What I wan't is a device that I can do ebook reading, web page browsing, multimedia playing/display both from on disk and streamed from a central server.  If I ever get my Pluto install working that is.  I also need to do IMAP mail, and remote desktop stuff.  So far, everything but the multimedia stuff has worked at some point, and konq defininately works better then the mini-web browser.

Bill

35
PocketPenguin / Body Design
« on: August 14, 2006, 12:02:47 pm »
That is a very nice idea, maybe each unit can have it's own battery, that could be used by the whole machine?  Power and charging through the USB connection...  Might want to use the micro USB connectors for this though because they wouldn't stick as far into the case.  Maybe all the power and charging could be through USB ports, rather than needing the round power connector?

Bill

36
PocketPenguin / Other Pda/phones To Get Ideas From
« on: August 13, 2006, 02:01:55 pm »
Here's another device..  Not really a PDA, but interesting placement of I/O stuff, and the camera swivels...

I-Note

Bill

37
Angstrom & OpenZaurus / 3.5.4.1 On Borzoi Using Akita Packages
« on: August 11, 2006, 04:20:15 pm »
Quote
Try this, much less hacky:

Code: [Select]
mount /dev/ /media/mountpoint; ipkg update; ipkg install task-bootstrap gpe-task-base gpe-task-settings gpe-task-pim gpe-task-apps xserver-kdrive-fbdev task-opie-base task-opie-base-applets task-opie-base-apps  task-opie-base-settings task-opie-base-pim  -o /media/mountpoint[div align=\"right\"][a href=\"index.php?act=findpost&pid=138042\"][{POST_SNAPBACK}][/a][/div]

Koen, I don't understand how that is less or more hacky than what I'm doing? That would leave the standard boot still to /dev/hda1, and you would essentially have the same stuff in two places.  

I really have no desire to boot multiple OS's, however I like the ease and beauty of OPIE, and the ability to run X stuff quickly of GPE,  Can you run the OPIE like applications under the GPE env, like pdaXrom?  

I did install and run both, but I noticed that running both OPIE and GPE result in my needing swap.  

On a side note, I also noticed that suspend and resume are alot slower than under the Sharp/Trisoft rom.

Keep in mind that I'm a newbie to this, and while I have been reading the forums, I'm sure that you have things that you assume everybody knows that I probably don't know...

Bill

38
Angstrom & OpenZaurus / 3.5.4.1 On Borzoi Using Akita Packages
« on: August 11, 2006, 04:16:25 pm »
The main thing I'm trying to get around is the size of the default root partition in the "ROM" it's only 32 meg (32768 bytes), and home is  89 meg (91136) bytes.  I tried pdaXrom yesterday, and it did some dangerous things...  They rewrite the boot code, and repartition the flash memory to actually be 121 meg.  The last bit I'd like to know how to do :-).  I got stuck trying to get my SanDisk CF WiFi working in pdaXrom, but that's another story.

  Long an short, How does the partition layout of the flash memory work anyways?  I think if I understood how to combine the standard root and home partitions into one root partition I would be all set.

Bill

39
Zaurus - pdaXrom / Beta4 Hostap Packages.
« on: August 10, 2006, 04:44:04 pm »
Hello,
I have a card that I got to work in OZ, using the Howto that was there for a Collie as a guide, yes it is a SanDisk ConnectPlus WiFi.  

I can't seem to find the equivalent packages to install for pdaXrom beta4,

When I try installing the hostap-drivers that say they include support for the prism3 chipset, it doesn't install looking for the script /etc/rc.d/init.d/pcmcia which I can't find anywhere on the system and in the feed/filelist.  I also don't really know if those packages contain 2.6.16 modules or not.  I did try installing the kernel-2.6.16 module package, but don't see the prism drivers there.

Where can I look for the packages/drivers I need?

Bill

40
C1000/3x00 Hardware / Compact Flash Vs 1.8in Hd
« on: August 10, 2006, 10:22:04 am »
Thanks for the picture.  

So can I infer that the micro drives (around 1") that are used are connector compatible with CF, but you were not able to have it recognized by the Z?  Possibly because we would need a driver change to tell the CF slot to be running in ATA mode?

Is the 1.8" drive also connector compatible with CF?  Leave aside the fact that the drive is the size of a PCMCIA card, and just focus on the connector right now.

Thanks for the info about the master/slave thing..  too bad.  I was thinking that it would be nice to put a flat cable hooked on the internal CF to wire up the interface to Wi-Fi and Bluetooth, still having the HD available.  This would result in no dangerous mods to the system board.  I don't have a steady enough hand, plus the C3100 is still too new to me.

I got the above idea from the sandisk 128M/Wi-Fi card, but since then I've found out that you can't use both the memory and the Wi-Fi at the same time on that card, which is very interesting.

Bill

41
PocketPenguin / Body Design
« on: August 10, 2006, 10:07:58 am »
I'd really like to be able to easily get at whatever internal storage is decided upon, without voiding the warranty (warranty??? WHAT warranty?).  That was my real reason for suggesting 2 CF slots, since I thought that the current design decision was to use the CF/ATA interface of the chip for an internal HD.  If we could design things to use the drives that Apple is using for their iPods that would be really nice :-) because those drives are very inexpensive compared to the CF HD's that the Z uses.  Standard off the shelf components are good for a project like this.

Bill

42
PocketPenguin / Body Design
« on: August 10, 2006, 10:00:10 am »
Could we put the application buttons by the screen?  That way we wouldn't need to have those touch screen psuedo buttons, and would free up space on the main keyboard for more regular keys without needing fn+.  Of course if you use the gull-wing design, the extra application buttons go there, right?  I personally don't mind that design, but if you use that, do the 5, 6, or 7 inch screens become more acceptable?  Do I hear widescreen?  800x400 anyone?

Bill

43
PocketPenguin / Body Design
« on: August 10, 2006, 03:01:11 am »
Hello,
  This a little bit premature, but, when designing these things, usually the system board layout has to work with the design of the shell that the board will inhabit.

  Some of the things that I recall about the current thinking for the body are:

1) Initial design will be a clamshell case like the SL-Cxx00 series
2) A 4" transreflective display 640x480 minimum
3) A hardware keyboard built in (just to be clear)
4) 1 CF Slot, CFIO capable - this is a no...
5) SD Slot, SDIO capable
6) 1 USB port, not sure if Mini or normal, Client or Host, or combined
7) 1 HDMI port for video out
8) 1 Audio out
9) 1 Audio in
10) 1 Camera
11) 1 Power input (again just to be clear)
12) Easy access to battery(ies)
13) Easy access to reset button
14) A Rocker switch (because the Z has it)
15) A Cancel and an OK button (because the Z has it)
16) A Power On/Suspend/Off button (no reason can't work like PC)
17) A speaker
18) A microphone
19) External antenna connection(s)
20) GSM Identity card access
21) a bunch of LEDs (HD, POWER, BT, WIFI, ...)
22) Fingerprint reader

Boy, that's alot of stuff.....

However, there can never be enough...  Some things I'd like to see in additon are:
1) 2 CF externally accessable.  No internal HD, I'd like to be able to easily switch out HD's.  This one will be very hard to accomplish, because of the realestate needed.
2) Both the USB Host and Client ports available in the full sized version.
3) I'd like to see 2 SD slots.
4) Maybe stereo speakers?

The keyboard should have some application keys some of which could be lighted different colors, to indicate on/off status, ie turn on bluetooth, or wi-fi.  The rest of the keyboard should be able to be backlit.

--edit-- added in the fingerprint reader, and make comment about CF slot

Bill

44
PocketPenguin / Batteries
« on: August 10, 2006, 02:34:06 am »
Hello,
  Would this type of battery work?  If so, then could the battery be integrated into where the hinge is?  I realize that this is probably not workable, but, cheap batteries, and the possibility of simplifying the system board layout by not putting the battery in the middle of it, ok, to one side.

2700ma AA rechargeables

45
Angstrom & OpenZaurus / 3.5.4.1 On Borzoi Using Akita Packages
« on: August 10, 2006, 02:20:54 am »
A better way would be if the mtdblock2 and mtdblock3 could be combined...  How could that be done?  Is there a risk of bricking the system?  In other words, if I screw up, should I still be able to get into the NAND restore function to put back a known good setup?  Pointers to URL's that describe the process would be acceptable here.

If I could do that, I could create one partition that was 121 meg and I wouldn't have to do the kludge with the extra symbolic links which is required because the usr tree isn't available in the early stages of the boot.

I'd still leave the HD partitions they way I described, although I noticed that the partitions seem to get unmounted and remounted as part of the boot process.

At this point I don't think the process is ready to be available for general consumption.  I'm re-examining the updater.sh scripts from the Akita and the Spitz installs to see about combining them in some way.  Don't really need to do the tar, since the root stuff is in a JFFS image file for Akita...  Is there a document for how that file is made?

Bill

Pages: 1 2 [3] 4 5