For this issue, yes, I do. I asked a simple question, that had a simple answer, which I appreciate. I didn't need the rest of the lecture about how I shouldn't be doing what I'm doing for whatever reason.
2. "Lots of ways to do this" isn't a useful comment. Using sysfs fits my model as far as I can tell. If you have a suggestion for a specific way that fits my model better, feel free to offer it. 3. That's not a rational comment. Android and Linux are open source. My question is about using those in particular. Just because it interfaces to something proprietary does not make it an inappropriate topic for this mailing list. On Feb 10, 7:05 pm, Greg KH <[email protected]> wrote: > On Thu, Feb 10, 2011 at 6:17 PM, jon.schell <[email protected]> wrote: > > 1. I've been reading some other support threads that you answer, and > > wow, you are really unimaginative and constrained. Yes, the pattern > > can be done from userspace, very slowly. Too slowly to be useful in > > fact. When someone asks a question, the best thing to do is answer > > the question and don't try to second-guess their motives or say "don't > > do it that way" when you don't know why they're doing it that way, or > > what the big picture of what they're doing is, which most people > > aren't going to be telling you for a simple question. > > Ok, you know best. > > > 2. No, I'm not creating a general kernel API, I'm creating something > > that only I will be using, for my purpose, so it can be "incorrect" or > > "not quite right" if I want. As I said, if you know of some other way > > to get a block of binary data into the driver, feel free to suggest > > it, but this way works great and will end my headache, so I don't care > > if it's proper. > > There are lots of ways to do this. Using sysfs is not the way. > > > 3. Proprietary code is not published. > > Then don't use open source and ask for questions on public mailing > lists. > > good luck, > > greg k-h -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
