> > Have somebody test the driver, > > or have although trouble with the chip? > > I haven't, but I'll add the people who brought the driver to the > kernel to CC. Maybe they can comment. It had some testing but in a limited configuration and mostly for a device that then got canned. Thus I can well believe the autocts/rts isn't set right, and IntOscen may well only get set if the firmware happens to do it etc > > Because i am really new with the kernel hacking, > > what are the next steps, build an patch? > > Doing patches (one per issue) might be an idea. It is usually easier > to talk about code. Reading Documentation/SubmittingPatches will > probably make the process easier. I would probably send it as four patches 1. A patch for the IntOscen configuration 2. A patch to fix autocts/rts 3. A patch to fix the register updates 4. A patch to add any platform specific stuff you need for your device. Thanks Alan -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
