Cantref of Penfro

The Cantref of Penfro was one of the seven cantrefi of the Kingdom of Dyfed. It subsequently became part of Deheubarth in around 950. It consisted of the long peninsular part of Dyfed south of the Eastern Cleddau and the Daugleddau estuary, and bordered on its landward side by Cantref Gwarthaf.[1] The name, meaning "land's end", derives from Pen ("end", literally "head") and "fro" ("populated area").[2] Its area was approximately 140 square miles (360 km2).

Location of the cantref of Penfro within ancient Dyfed

It was divided into two commotes: Cwmwd Penfro in the southwest and Cwmwd Coedrath in the northeast, as shown in the map. The eastern part of Cwmwd Penfro was sometimes called Cwmwd Maenorbier, and the northern part of Cwmwd Coedrath was sometimes called Cwmwd Arberth, but both these were post-Norman lordships, and were probably not genuine commotes.[3] Its civil headquarters were at Pembroke: Rhoscrowther or Penally might have been its ecclesiastical centre.[4]

The cantref was made part of the Norman March in the 12th century, and many castles were built, including those of Carew, Manorbier, Narberth, Pembroke,[5] and Tenby. The area became English-speaking, as it continues today, except in the northern part of Narberth parish.

At the time of the 1535 Acts of Union, the cantref was split between two newly formed hundreds, when Cwmwd Penfro became Castlemartin Hundred,[6] and Cwmwd Coedrath was merged into Narberth Hundred.

Notes
  1. Richards, Melville, Welsh Administrative and Territorial Units, UoW Press, 1969, p 309
  2. Charles, B. G., The Placenames of Pembrokeshire, National Library of Wales, Aberystwyth, 1992, ISBN 0-907158-58-7, p 671
  3. Charles ibid, p 671
  4. Williams, A. H., An Introduction to the History of Wales: Volume I: Prehistoric Times to 1063, UoWP, 1941, p 120
  5. John Davies (25 Jan 2007). A History of Wales. Penguin UK. p. 171. Retrieved 16 June 2012.
  6. Nicholas Carlisle (1811). A topographical dictionary of Wales. Retrieved 16 June 2012.
gollark: That isn't what's happening in this case.
gollark: I know. It seems poorly designed in some areas. Apparently tasks can be garbage collected inconveniently.
gollark: An asyncio task I have interfacing with MPD randomly exits with no clear reason why and no output.
gollark: Also, do you have any idea why python might be pythonoforming?
gollark: We don't host any yet.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.