READY EAT PANCAKES

Brand Owner (click to sort) Address Description
LA CRÊPERIE REAL BELGIAN CREPES J. Vink Jr. Development B.V. Baanhoek 186 3361 GN SLIEDRECHT Netherlands ready-to-eat pancakes; ready-to-eat mini pancakes; ready-to-eat puffed pancakes; ready-to-eat American pancakes;The mark consists of the wording LA CRÊPERIE in white above the wording REAL BELGIAN CREPES in beige, all within a brown circle.;The color(s) brown, beige and white is/are claimed as a feature of the mark.;
MA RAEBURN'S De Bioderij B.V. Baanhoek 186 Sliedrecht 3361 GN Netherlands Ready-to-eat pancakes; ready-to-cook and ready-to-serve frozen meals and packaged meals consisting primarily of pasta and rice;The name MA RAEBURN'S identifies a living individual whose consent is of record.;
VINNY FINCH J. Vink Jr. Development B.V. Baanhoek 186 3361 GN SLIEDRECHT Netherlands ready-to-eat pancakes; ready-to-eat mini pancakes; ready-to-eat puffed pancakes; ready-to-eat American pancakes;Vinny Finch does not identify a living individual.;
VINNY FINCH De Bioderij B.V. Baanhoek 186 Sliedrecht 3361 GN Netherlands ready-to-eat pancakes; frozen, prepared and packaged entrees consisting primarily of pasta or rice;frozen, prepared and packaged entrees consisting primarily of meat, fish, poultry, potatoes and vegetables;The name(s), portrait(s), and/or signature(s) shown in the mark does not identify a particular living individual.;
 

Where the owner name is not linked, that owner no longer owns the brand

    
Technical Examples
  1. Transactions are scheduled over a half duplex link between a first device, such as an IO unit, and a second device, such as a memory controller. Information flowing over the half duplex link is divided into a plurality of service periods, and an isochronous transaction, such as an isochronous memory read or write, is scheduled in a service period N if the isochronous transaction is ready to be serviced before service period N at the first or second device. An asynchronous transaction ready to be serviced at the first or second device, such as an asynchronous memory read or write, is scheduled if no isochronous transaction is ready to be serviced. The asynchronous transaction may be scheduled by (a) scheduling an asynchronous transaction ready to be serviced at the first device if no asynchronous transaction is ready to be serviced at the second device; (b) scheduling an asynchronous transaction ready to be serviced at the second device if no asynchronous transaction is ready to be serviced at the first device; and (c) scheduling an asynchronous transaction ready to be serviced at the first or second device, according to an arbitration algorithm, if asynchronous transactions are ready to be serviced at both the first device and the second device. The amount of buffer space available in the first or second device may also be used to schedule asynchronous transactions.