>> The reason 'intelblocks' is in the include path is because the include >> headers are namespaced. e.g. #include <intelblocks/blah.h>.
My +2 to Aaron's comment, that’s the only reason to create "intelblocks". Thanks, Subrata -----Original Message----- From: Aaron Durbin [mailto:[email protected]] Sent: Monday, June 5, 2017 9:11 PM To: Paul Menzel <[email protected]> Cc: Coreboot <[email protected]>; Banik, Subrata <[email protected]> Subject: Re: [coreboot] What does *intelblocks* mean? On Mon, Jun 5, 2017 at 2:48 AM, Paul Menzel <[email protected]> wrote: > Dear coreboot folks, > > > In commit a554b0c5b7 (soc/intel/common/block: Add Intel XHCI driver > support) [1] the directory > `src/soc/intel/common/block/include/intelblocks` is created. > > Could somebody please help me, what *intelblocks* means here, and why > *intel* is twice in the path? It's common code to be used for intel SoCs. 'ipblock' would be more appropriate, but I think people didn't want to freak anyone out with the name 'ip'. The reason 'intelblocks' is in the include path is because the include headers are namespaced. e.g. #include <intelblocks/blah.h>. > > > Thanks, > > Paul > > > [1] https://review.coreboot.org/18221/ > > -- > coreboot mailing list: [email protected] > https://mail.coreboot.org/mailman/listinfo/coreboot -- coreboot mailing list: [email protected] https://mail.coreboot.org/mailman/listinfo/coreboot
