Contrary to what my tag implies, I am a bit of kernel compiling n00b. I am hoping that someone may assist in validating my understanding of what needs to be done in my particular scenario. Here it goes... (apologies for the long-windedness)

I am looking to integrate a CrystalFontz 634 USB LCD Disply into my system and use the LCDProc as the software that supplies my display data.

According to the directions found at LCDProc lcdproc.omnipotent.net it states that I should add a few tweaks to the kernel source files prior to compiling. And I quote...

"In linux-2.4.20/drivers/usb/serial/, there are two files that need to be changed to add the vendor and product IDs in use by the serial displays: ftdi_sio.c and ftdi_sio.h. The files are the serial drivers for FTDI’s 8U232AM chips, which is what the 632 & 634 use to convert from USB to serial."

Here are the tweaks (cut & pasted) from webbastards.com/projects/CF632/CF632-USB.html

The actual details of the patch are as follows:


--- serial/ftdi_sio.h 2003-02-13 21:59:58.000000000 -0500
+++ /home/wayne/linux-2.4.20/drivers/usb/serial/ftdi_sio.h 2002-11-28 18:53:14.000000000 -0500

@@ -25,14 +25,6 @@

#define FTDI_NF_RIC_VID 0x0DCD /* Vendor Id */
#define FTDI_NF_RIC_PID 0x0001 /* Product Id */
-/*
- * The following are the values for the Crystal Fontz Orbital LCD displays,

- * which use the 8U232AM
- */
-#define FTDI_CF_VID FTDI_VID /* Crystal Fontz Product Id */
-#define FTDI_CF_0_PID 0xFC08 /* Crystal Fontz Product Id */
-#define FTDI_CF_1_PID 0xFC09 /* Crystal Fontz Product Id */
-
#define FTDI_SIO_RESET 0 /* Reset the port */
#define FTDI_SIO_MODEM_CTRL 1 /* Set the modem control register */
#define FTDI_SIO_SET_FLOW_CTRL 2 /* Set flow control register */

--- serial/ftdi_sio.c 2003-02-13 22:00:25.000000000 -0500
+++ /home/wayne/linux-2.4.20/drivers/usb/serial/ftdi_sio.c 2002-11-28 18:53:14.000000000 -0500

@@ -154,8 +154,6 @@

static struct usb_device_id id_table_8U232AM [] = {
{ USB_DEVICE(FTDI_VID, FTDI_8U232AM_PID) },
{ USB_DEVICE(FTDI_NF_RIC_VID, FTDI_NF_RIC_PID) },
- { USB_DEVICE(FTDI_CF_VID, FTDI_CF_0_PID) },
- { USB_DEVICE(FTDI_CF_VID, FTDI_CF_1_PID) },
{ } /* Terminating entry */
};

@@ -164,8 +162,6 @@

{ USB_DEVICE(FTDI_VID, FTDI_SIO_PID) },
{ USB_DEVICE(FTDI_VID, FTDI_8U232AM_PID) },
{ USB_DEVICE(FTDI_NF_RIC_VID, FTDI_NF_RIC_PID) },
- { USB_DEVICE(FTDI_CF_VID, FTDI_CF_0_PID) },
- { USB_DEVICE(FTDI_CF_VID, FTDI_CF_1_PID) },
{ } /* Terminating entry */


So, the way I look at it is that I need to ADD the entries above to the files specified in the specific locations within the files (@@ -25,14 +25,6 @@ and @@ -154,8 +154,6 @@). I do not need to CHANGE the existing entries nor DELETE the existing entries in the specified files.

Am I on the right path? Thanks in advance...
sub-"genius"

Yup add the entries. After that do the recompile, and enjoy the flat screen.

Actually, this looks like a DIFF file - you would have to use the diff utility to update those files from this one. Have to check the man page, but the diff uitility takes this file as input, then modifies the target files at the appropriate locations where the changes should be.

yes, use the diff command, but use the backup option for diff, or copy the original file, in case you do something wrong. That way you won't lose the original file.

I get what ur saying about the diff utility, but the changes that are listed above are not actually within a separate and distinct file per se. The changes are written into an html procedural document located at the URL posted above. Is it possible to cut and paste the changes into a diff utility "consumable: document?

-Sub

Got the USB LCD working and I didn't even have to REcompile

I just compiled from 2.4.21, which includes support for my brand of USB LCD (CrystalFontz).

Bless you all!