memblock structure

There are three memblock_type members memory , reserved and physmem in memblock structure. What is the significance of each member? regards, Ronit ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org

Re: Bios , Mbr, Grub

OK ! THANKS A LOT ! Gnoleba 2016-07-05 12:32 GMT+00:00 Daniel. : > It is not a link, it's a command, the link is this: > http://git.savannah.gnu.org/cgit/grub.git/tree/ > > 2016-07-05 3:17 GMT-03:00 Ricardo Ribalda Delgado < > ricardo.riba...@gmail.com>: > >

Re: what is the minimal version of make supported for building the kernel?

On Mon, Jun 20, 2016 at 5:15 AM, Robert P. J. Day wrote: > now, Documentation/Changes currently does indeed state: > > Current Minimal Requirements > > ... snip ... > o GNU make 3.80# make --version > > but

Re: memblock structure

On Wed, Jul 06, 2016 at 06:12:50PM +0530, Ronit Halder wrote: > There are three memblock_type members memory , reserved and physmem in > memblock structure. > What is the significance of each member? According to https://github.com/0xAX/linux-insides/blob/master/mm/linux-mm-1.md they describe

Re: Bios , Mbr, Grub

> On 04-Jul-2016, at 2:30 pm, Gnoleba GNOGBO wrote: > > Hi ! > > I had read a lot of book and link about initialization of the boot starting > of linux. > > I read that , after the post by the bios the mbr is loaded in memory which > routine load this sector ? This is

memblock structure

There are three memblock_type members memory , reserved and physmem in memblock structure. What is the significance of each member? regards, Ronit ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org

Re: spi can't read more than 64 bytes

Hi, isn't it possible that your hal_frame_read be called again prior rf_rx_completion_handler is called, and because of this calling spi_message_init on a spi_message that is in spi queue yet? 2016-07-06 10:25 GMT-03:00 Moti Cohen : > Hi all, > > > > I'm trying to write a

Re: Bios , Mbr, Grub

Hi ! Thanks for your answears. Can you give le the link where i can find "Understanding the linux system startup " please ? Regards Gnoleba Le 6 juil. 2016 04:00, "arshad hussain" a écrit : > > > On 04-Jul-2016, at 2:30 pm, Gnoleba GNOGBO wrote: >

Re: Memory pages not released by the filesystem after a truncate

On Wed, Jul 6, 2016 at 6:24 AM, Houssem Daoud wrote: > Hi, > > My system experiencing problems with atomic memory allocations. Device > drivers are not able to allocate contiguous memory regions due to a high > fragmentation level. > > At the time of failure:

spi can't read more than 64 bytes

Hi all, I'm trying to write a kernel device driver for a Freescale imx6 processor based board. This driver is using spi to communicate with a radio module (using linux spi.c). I managed to wr/rd from the module, however once I'm trying to read more than 64 bytes I'm getting coruppted data.

Bio flags

Hi, I am porting some of file system related code from 3.0.101 kernel to 4.4.13 kernel and found that the number of bio flags have been reduced from 13 to 8 and some of the which been removed are : BIO_UPTODATE BIO_RW_BLOCK BIO_EOF BIO_EOPNOTSUPP ... I was unable to find much in the