--
You received this message because you are subscribed to the Google Groups "embox-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to embox-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/embox-devel/23471e1e-8620-2634-b385-2f08917df387%40gmail.com.
Anton :
I'm just getting acquainted with Embox now. What I'm seeing, I think, is that the whole thing, for Raspberry Pi ARM anyway, is running at the same boot exception level.
Honestly, I'm just getting up to speed with that kind of thing but what it looks like, is that with using different exception levels, you can have different vector tables for each exception level. This would be nice to make kernel more robust and guarded against other code running at a lower exception level. I'm expecting that would be an invasive change for the HAL of ARM. I'll likely have to keep that parked for a while until I experiment more with it.
The other thing I'm looking at, you may see in my repos a fork of fbcp-ili9341 (https://github.com/kpishere/fbcp-ili9341). I know this driver quite well, it is very independent of linux OS and any other drivers. I'd managed to make it work with touch screen ability, more as a kludge really, in Linux kernel -- it was quite awkwardly done. I think it would work very nicely in Embox!
Only, I'm not seeing a like component right now to this. Basically, this bit of code would be copying frame buffer changes to an SPI device and would also be reading back touch events from same pipeline. Note that the touch events can only be read when the screen is being updated! So, in linux, I'd gotten around that by always drawing a cursor or touch point on the screen.
If you had any pointers on where you'd like to see this go or which driver would be best to model after, I'm all ears. Regardless, I go through your documentation and see what I can do.
Like, where would this driver show up under your devices?
.\driver\lcd\ili9341
.\driver\spi_lcd
.\driver\lcd_spi
.\driver\input\touchscreen\ili9341
I think I'm partial to the last path here as the framebuffer
copying, besides taking over the SPI bus fully, is quite
transparent to other tasks, the only interface point to other
tasks is the touchscreen.
k.
I'm just getting acquainted with Embox now. What I'm seeing, I think, is that the whole thing, for Raspberry Pi ARM anyway, is running at the same boot exception level.
Honestly, I'm just getting up to speed with that kind of thing but what it looks like, is that with using different exception levels, you can have different vector tables for each exception level. This would be nice to make kernel more robust and guarded against other code running at a lower exception level. I'm expecting that would be an invasive change for the HAL of ARM. I'll likely have to keep that parked for a while until I experiment more with it.
The other thing I'm looking at, you may see in my repos a fork of fbcp-ili9341 (https://github.com/kpishere/fbcp-ili9341). I know this driver quite well, it is very independent of linux OS and any other drivers. I'd managed to make it work with touch screen ability, more as a kludge really, in Linux kernel -- it was quite awkwardly done. I think it would work very nicely in Embox!
Only, I'm not seeing a like component right now to this. Basically, this bit of code would be copying frame buffer changes to an SPI device and would also be reading back touch events from same pipeline. Note that the touch events can only be read when the screen is being updated! So, in linux, I'd gotten around that by always drawing a cursor or touch point on the screen.
Like, where would this driver show up under your devices?