On Tue, Aug 19, 2014 at 02:25:57PM +0200, Cestonaro Thilo wrote: > > You might want to step back and describe what you are wanting to do in > > the first place before wanting to add a new line discipline. > > > > > Ok. > Imagine you have two chips, one is the cpu and the other one is a device > which needs to be configured, accessed, talked to via uart. > The both chips are hardwired via uart. > Now I want to communicate from the kernel module with the device. Why within the kernel? Why not do the communication from userspace? > let the device be a RTC Device which has a UART interface. How do you talk to this UART? Through a "normal" serial chip that the kernel already has a driver for, or through some other hardware control interface? > And I don't want to rewrite all the uart device stuff of the cpu uart > device. What do you mean by this? > As a i2c client doesn't implement master_xfer or whatever the transfer > methods are called in the i2c controller module. > It just does a i2c->write(reg, value) and I need something equivalent > like uart->send(data, len); and uart->handle_recieved = > my_recieved_data_handler; Do that in userspace :) thanks, greg k-h -- 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
