Beech LCD patch
Could somebody please commit the following patch to linuxppc_2_4_devel. It fixes a bug in the Beech/405LP LCD driver. I'd commit it myself, except me doing a push seems to break the tree at the moment. diff -ruN linux.orig/drivers/video/ibmlcdfb.c linux/drivers/video/ibmlcdfb.c --- linux.orig/drivers/video/ibmlcdfb.c Fri Aug 9 19:16:04 2002 +++ linux/drivers/video/ibmlcdfb.c Fri Aug 9 19:15:51 2002 @@ -1218,7 +1218,8 @@ int ncolors; const struct ibmlcdfb_info *info = (struct ibmlcdfb_info *) inf; - ncolors = 1 bpp_from_par(info-gen.info.par); + ncolors = bpp_from_par(info-gen.info.par); + if (regno = ncolors) return -EINVAL; @@ -1249,7 +1250,8 @@ int ncolors; struct ibmlcdfb_info *info = (struct ibmlcdfb_info *) inf; - ncolors = 1 bpp_from_par(info-gen.info.par); + ncolors = bpp_from_par(info-gen.info.par); + if (regno = ncolors) return -EINVAL; -- David Gibson| For every complex problem there is a david at gibson.dropbear.id.au | solution which is simple, neat and | wrong. http://www.ozlabs.org/people/dgibson ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
First steps to OCP device model integration
On Fri, Aug 09, 2002 at 12:41:29PM -0700, akuster wrote: David Gibson wrote: THe patch below implements the first steps in transitioning the handling of 4xx OCP devices to the unfied device model (in 2.5). So far the code just registers an ocp bus and registers each device described in core_ocp on that bus. The next step is to convert the actual device drivers so that that they register with the unified driver tree rather than through the old ocp_register() mechanism. I will commit this shortly unless there are serious objections. I object seriously. Some of what you have might be useful.:) OCP is not just for 4xx. In Sure, details, changing names is easy. At the moment 4xx is the only thing using OCP so we might as well get it working for that before worrying too much about anything else. fact the name may need to change. I have been working on overhalling this interface and testing the ideas before having a review of the changes. I am on the hook to Paul and others to get this out in the open to discuss and am not ready. So if you could just relax and wait I So how about you tell us about this new scheme of yours. This is not a difficult problem, and you've been making intermittent mutterings for months. would appriciate it. I would rather see the 2.5 kernel boot on a few 4xx boards OCP support is currently the main thing lacking for that. -- David Gibson| For every complex problem there is a david at gibson.dropbear.id.au | solution which is simple, neat and | wrong. http://www.ozlabs.org/people/dgibson ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
embedded Qt
Hello Wolfgang, we have the full QT Embedded Demo ($QTDIR/examples/launcher) running on the TQM823L modules. So far it's working fine. It's based on the release qt-embedded-free-3.0.1. In case you are interested, I could send you my patch plus some build instructions. Could you post these on the list or make them available on an ftp site? Thanks, Bart ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RequestIO : Resourse in Use
An embedded and charset-unspecified text was scrubbed... Name: not available Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20020812/e7a9b93c/attachment.txt
USB support
Hi! I'm new to this list. :) I'd just like to know if usb and uhci or ohci support for TQM board with MPC860 is already implemented somewhere. I'm using 2.4.4 kernel from DENX and when I include support for any of (X)HCI options it will not compile. by, ivo ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
[PATCH] Two little fixes for linuxppc_devel-2.4.19
David M?ller (ELSOFT AG) wrote: Hello The attached patch fixes the following issues: - arch/ppc/kernel/ocp.c missing export of ocp_get_pm - drivers/net/ibm_ocp/ibm_ocp_enet.h shifting of PM bits is done in wrong direction Dave Great, looks good Thanks David, Armin ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Beech LCD patch
On Mon, Aug 12, 2002 at 10:42:04AM +1000, David Gibson wrote: Could somebody please commit the following patch to linuxppc_2_4_devel. It fixes a bug in the Beech/405LP LCD driver. I'd commit it myself, except me doing a push seems to break the tree at the moment. With the magic of BK_USER/BK_HOST, pushed. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
linuxppc_2_4_dev tree
Hi folks, How can I build a kernel image with target filesystem mounted via NFS fro mthe dev tree? The dev tree doesn't seem to have the target filesystem directory structure like the ones distributed by MVista for NFS mount. If it's not nfs mountable, can I create a ramdisk filesystem together with the kernel image? Thanks, --Khai ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
linuxppc_2_4_dev tree
On Mon, Aug 12, 2002 at 01:51:33PM -0700, Khai Trinh wrote: How can I build a kernel image with target filesystem mounted via NFS fro mthe dev tree? The dev tree doesn't seem to have the target filesystem directory structure like the ones distributed by MVista for NFS mount. Er, I don't quite follow you. If you want to build a kernel from the _devel tree which mounts it's filesystem over NFS, you need to start with the config file from the MVL kernel, and then turn on CONFIG_CMDLINE_BOOL, and have a command line of 'ip=on'. If it's not nfs mountable, can I create a ramdisk filesystem together with the kernel image? Yes. Make the filesystem image, gzip it, and place it was 'arch/ppc/boot/images/ramdisk.image.gz', and then do 'make zImage.initrd' -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
linuxppc_2_4_dev tree
Khai Trinh wrote: How can I build a kernel image with target filesystem mounted via NFS fro mthe dev tree? The dev tree doesn't seem to have the target filesystem directory structure like the ones distributed by MVista for NFS mount. The bitkeeper tree is the kernel only. A root filesystem you have to make or get elsewhere. I've had good luck with the DENX Embedded Linux Development Kit. Here: http://www.denx.de/ELDK/ It has a working rootfs that can be mounted via NFS. You can then pare that down to make it smaller if you need to. Busybox and Tinylogin are also useful for creating user-land to go with your kernel. http://www.busybox.net/ http://tinylogin.busybox.net/ Busybox can act as init, though the inittab needs to be a bit different than a regular inittab, if I remember right. I found getting a satisfactory rootfs was not exactly easy. Not too hard, but a lot of details to get just right, especially if you need to make it small. You'll want to make a script to create your root fs, which you can then use from a kernel which mounts it by NFS (useful for debugging applications) or by cramfs/initrd setup where the whole image, kernel and rootfs, is loaded into RAM. Hope that helps some. -- steve ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
